SC WordPress malware shown as a server linked to PHP files, database storage, shared memory and a blockchain network. SC WordPress malware shown as a server linked to PHP files, database storage, shared memory and a blockchain network.

SC WordPress malware builds a self-healing backdoor mesh

Sucuri analyst Gabriel Barbosa describes SC as a WordPress backdoor mesh that can restore its files from database, shared memory and scheduled tasks. The cleanup starts by stopping execution, then removing every persistence point in the right order.

A backdoor that returned seconds after deletion led Sucuri security analyst Gabriel Barbosa to document SC, a WordPress infection built to restore its own components. In a September 30, 2026 analysis, Barbosa describes loaders and drop-ins spread across files, the database and shared memory. Site owners dealing with a repeat infection need to find those copies and follow the cleanup sequence, not just delete the visible plugin.

SC WordPress malware is not a single file to remove. Its components can rewrite one another, while copies stored outside the file system can restore the infection on a later request or scheduled run. Neutralize the PHP prepend first, clear database, shared-memory and cron persistence, remove database triggers and hidden administrators, then delete the malicious files together and rescan.

How SC WordPress malware rebuilds itself

Sucuri says the infection has at least eight coordinated components. The chain starts with a .user.ini directive that sets auto_prepend_file. PHP runs the selected loader before requests in that directory tree, including requests that never reach WordPress.

The prepend points to a visible PHP shim. That file includes a hidden, dot-prefixed loader if one exists. The hidden loader can rebuild a fake must-use plugin from an existing plugin copy, an encoded cache stub or a ZIP restore bundle. Sucuri’s example files include wp-content/c1b12371.php and wp-content/.c1b12371.php, though filenames vary between sites.

More components provide other ways to restore the payload. The wp-content/db.php drop-in carries it as a gzip-and-base64 blob. The advanced-cache.php drop-in searches for copies in the must-use plugin, regular plugin, shared memory, ZIP bundles and database. A bounded block appended to the active theme’s functions.php can also rewrite the plugin.

The backdoor appears in two places: as a must-use plugin and as a regular plugin. Example paths include wp-content/mu-plugins/hyper-engine-kit.php and a copy under wp-content/plugins/hyper-engine-kit/. The regular plugin includes a plausible settings page, shortcode and activation hook. The must-use copy loads automatically and stays out of the ordinary active-plugin list.

Blockchain gateways carry operator instructions

The payload hides its plugin entry from WordPress admin and update views. It communicates with operators through roughly 20 public Ethereum RPC gateways, using smart-contract methods to retrieve instructions. Sucuri describes those gateways as part of the command channel. Blocking one fixed server is not the answer the report points to.

SC fingerprints each site by collecting information that includes its URL, host, WordPress and plugin versions, active themes, must-use plugins and administrator session tokens. It encrypts and sends that bundle to a resolved endpoint. A response can contain front-end JavaScript to inject, PHP to install, or instructions to deactivate and delete security plugins.

The malware can create or adopt a hidden administrator, hide the account from user views and forge authentication cookies for it. A magic request parameter can trigger a response before WordPress finishes loading. Hooks and filters in the payload can regenerate the loaders, drop-ins, theme block, database copy, ZIP bundle and shared-memory copy.

Persistence extends beyond WordPress files

Sucuri found a gzip-and-base64 payload in an options-table row with a random name, another copy in a System V shared-memory segment, and WordPress cron hooks that can trigger redeployment. Removing the visible plugin and drop-ins does not remove those copies. Any one of them can put files back.

The report also describes database triggers in related SC variants that recreate an administrator when a user record is inserted. Delete the account without checking for such a trigger and the database can create it again, even after the files are restored.

During an investigation, check for unexpected PHP in db.php and advanced-cache.php, marked blocks in the active theme, and prepend directives in .user.ini or related configuration files. Look for paired fake plugin copies, ZIP files with random names, suspicious options rows, shared-memory contents, hidden administrators and outbound Ethereum RPC requests. None of those signs alone proves an SC infection. A file that returns does show that some persistence point remains, or that the original entry path is still open.

Use the cleanup order Sucuri recommends

Order matters. Remove files while a loader is still active and it can restore them immediately. Sucuri also warns that PHP caches the prepend setting. If the target file is deleted while that cache is warm, PHP requests on the account can fail until the cache expires.

  1. First, make the prepend target inert. Then remove the auto_prepend_file directive from .user.ini, php.ini and .htaccess where present.
  2. Next, clear off-disk persistence. Remove the malicious options row and related control options or transients, purge the shared-memory segment, and clear malicious cron hooks. If the segment belongs to another hosting account, the host or that account may need to remove it.
  3. Check for database triggers that recreate accounts before deleting the hidden administrator. Remove any orphaned option tied to that account as well.
  4. Delete the malicious files in one pass: loaders, both fake plugin copies, restore ZIP files and infected drop-ins. In the legitimate theme file, remove only the bounded injected block.
  5. Rescan and monitor the affected paths for returning files. If a component reappears, check the database, shared memory, scheduled tasks and possible entry point instead of deleting that file again.

For site owners and incident responders, a repeat infection calls for a persistence check across files, database and memory. Keep a clean backup, and coordinate with the host if shared-memory access or server-level configuration is outside your control.

FAQ

What is SC WordPress malware?

SC is the name Sucuri uses for a WordPress malware family marked by SC-style injected content. Its backdoor is spread across loaders, drop-ins, plugin copies and off-disk persistence.

Why does the malware return after file deletion?

A surviving component can rebuild the others. The payload may also remain in a database option, shared-memory segment or scheduled task, then restore files on a later request or cron run.

What should be removed first?

Neutralize the auto_prepend_file target before deleting it, then remove off-disk copies and scheduled persistence. Check database triggers and hidden administrators before deleting all malicious files in one pass, then rescan and monitor.

Next step: If your site keeps restoring unfamiliar files, stop repeating file-only cleanup. Audit its database rows, cron hooks, shared memory and PHP prepend settings.

Leave a Reply

Your email address will not be published. Required fields are marked *