Skip to navigation

Threat reportMalwareTL-2026-6157

SC WordPress Malware: Self-Healing Mesh of Loaders, Drop-Ins and Ethereum-Smart-Contract-Controlled Backdoor

highACTIVE

Sucuri describes 'SC' (named for its 'SC_' markers), a WordPress infection whose payload exists in at least eight places on disk, in the database and in shared memory that can each rebuild the others. The backdoor hides from plugin lists and update checks, reads C2 instructions from an Ethereum smart contract via roughly twenty public RPC gateways, creates a hidden administrator with forged auth cookies, and can inject JavaScript, install PHP and remove security plugins. First disclosed .

Key facts

IdentifiersTL-2026-6157
Also known asSC WordPress malware, SC_ marker WordPress backdoor, Hyper Engine Kit fake plugin
SeverityHIGH
First disclosed
Affected productsWordPress WordPress sites (core, plugins, themes; PHP hosting with .user.ini/auto_prepend_file support)
MalwarePHP, SC WordPress malware
MITRE ATT&CK techniquesT1027 Obfuscated Files or Information, T1027.013 Encrypted/Encoded File, T1036.005 Match Legitimate Resource Name or Location, T1053.003 Cron, T1056.003 Web Portal Capture, T1059 Command and Scripting Interpreter, T1059.007 JavaScript, T1070.006 Timestomp, T1071.001 Web Protocols, T1082 System Information Discovery, T1098 Account Manipulation, T1102.001 Dead Drop Resolver and 7 more in the attack flow
MotivationUNKNOWN
Target sectorsecommerce, news - media, small business, web hosting
Target regionsGlobal
Detection rules9 (1 shown free)
Sources6 cited sources

Detection coverage

As of 2026-11-16, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6157 across Splunk SPL, Microsoft KQL and Sigma, covering 19 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: SC WordPress Malware - hyper-engine-kit, db.php/advanced-cache.php Drop-In and Hidden Loader File Placement

Detects creation/modification of SC WordPress backdoor on-disk components (TL-2026-6157): wp-content/db.php (SC_DB_BEGIN), advanced-cache.php/object-cache.php (SC_ADV_*), the fake hyper-engine-kit mu-plugin and plugin copies, dot-prefixed hidden loaders such as wp-content/.c1b12371.php and .g_*.php guard stubs. Relies on auditd watch rules on wp-content. The self-healing mesh rewrites these files whenever one is removed, so repeated hits on the same host are a strong signal of incomplete cleanup.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1505.003, T1036.005, T1564
  • Data sources: linux_audit (auditd PATH records, index=linux), Microsoft Defender for Endpoint DeviceFileEvents, Sysmon for Linux FileCreate
  • Severity: high
  • Confidence: high

Splunk SPL

index=linux sourcetype=linux_audit type=PATH
    (name="*/wp-content/db.php" OR name="*/wp-content/advanced-cache.php" OR name="*/wp-content/object-cache.php"
     OR name="*/wp-content/mu-plugins/hyper-engine-kit.php" OR name="*/plugins/hyper-engine-kit/*"
     OR name="*/wp-content/.*.php" OR name="*/wp-content/cache/.g_*.php" OR name="*/wp-includes/.g_*.php")
| eval ioc_class=case(
    like(name,"%hyper-engine-kit%"), "fake_plugin_hyper_engine_kit",
    like(name,"%/.g_%"), "guard_stub_g_php",
    match(name,"/wp-content/[.][^/]+[.]php$"), "hidden_dotfile_loader",
    match(name,"/wp-content/(db|advanced-cache|object-cache)[.]php$"), "dropin_SC_DB_SC_ADV",
    true(), "other")
| stats count earliest(_time) as first_seen latest(_time) as last_seen values(nametype) as nametype by host name ioc_class
| convert ctime(first_seen) ctime(last_seen)
| table host name ioc_class nametype count first_seen last_seen

Microsoft KQL

DeviceFileEvents
| where Timestamp > ago(24h)
| where ActionType in ("FileCreated", "FileModified", "FileRenamed")
| where FolderPath has "/wp-content" or FolderPath has "/wp-includes"
| where (FolderPath endswith "/wp-content" and FileName in~ ("db.php", "advanced-cache.php", "object-cache.php"))
    or (FolderPath has "/wp-content/mu-plugins" and FileName =~ "hyper-engine-kit.php")
    or FolderPath has "/plugins/hyper-engine-kit"
    or (FolderPath endswith "/wp-content" and FileName matches regex @"^\.[^.]+\.php$")
    or FileName matches regex @"^\.g_.*\.php$"
| project Timestamp, DeviceName, ActionType, FolderPath, FileName, SHA256, InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessAccountName
| order by Timestamp desc

Sigma

title: SC WordPress Malware Drop-In, Hidden Loader and Fake hyper-engine-kit Plugin File Placement
id: 3f9c2a71-5b8e-4d1a-9c60-7e2a1b4d8f01
status: experimental
description: Detects creation or modification of the SC WordPress backdoor on-disk components - db.php / advanced-cache.php / object-cache.php drop-ins, the fake hyper-engine-kit mu-plugin and plugin copies, dot-prefixed hidden loaders in wp-content and .g_*.php guard stubs.
references:
    - https://blog.sucuri.net/2026/09/sc-wordpress-malware-a-self-healing-mesh-of-loaders-drop-ins-and-a-blockchain-controlled-backdoor.html
    - https://www.monarx.com/press-news/the-wordpress-infection-that-rebuilds-itself-faster-than-you-can-delete-it
author: Threadlinqs Team
date: 2026/11/16
tags:
    - attack.persistence
    - attack.t1505.003
    - attack.defense-evasion
    - attack.t1036.005
    - attack.t1564
logsource:
    category: file_event
    product: linux
detection:
    selection_dropin:
        TargetFilename|re: '/wp-content/(db|advanced-cache|object-cache)\.php$'
    selection_fake_plugin:
        TargetFilename|contains: '/hyper-engine-kit'
    selection_hidden_loader:
        TargetFilename|re: '/wp-content/\.[^/]+\.php$'
    selection_guard_stub:
        TargetFilename|re: '/(wp-includes|wp-content|wp-content/cache)/\.g_[^/]*\.php$'
    condition: 1 of selection_*
falsepositives:
    - Caching plugins (W3 Total Cache, WP Super Cache, LiteSpeed Cache, Redis Object Cache) legitimately create advanced-cache.php, object-cache.php or db.php
    - Legitimate database drop-ins such as Query Monitor or HyperDB
level: high

Known false positives:

  • Caching/object-cache plugins legitimately create advanced-cache.php, object-cache.php and db.php
  • Legitimate database drop-ins (HyperDB, Query Monitor) and deployment tooling writing to wp-content

Tuning notes: Requires an auditd watch such as -w /var/www -p wa -k wp_files. Allow-list hosts/paths where a known caching plugin owns advanced-cache.php/object-cache.php by comparing file hashes. The visible shim (wp-content/c1b12371.php) varies per site, so pair this with the auto_prepend_file detection (KQL-001). Any hit on hyper-engine-kit or .g_*.php should not be tuned out.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • SC WordPress Malware - auto_prepend_file Shim Directive and PHP mtime Back-Dating · unlock with TL Creds
  • SC WordPress Malware - Off-Disk wp_options Payload and WP-Cron Persistence Markers in MySQL Audit Logs · unlock with TL Creds
  • SC WordPress Malware - PHP/Web Server Process Outbound Connection to Ethereum RPC Gateways (eth_call C2) · unlock with TL Creds
  • SC WordPress Malware - Web Server Process Rebuilding mu-plugin, Drop-In or Hidden Loader · unlock with TL Creds
  • SC WordPress Malware - Hidden Administrator and SC Cron Hook Persistence via wp-cli / mysql Client · unlock with TL Creds
  • SC WordPress Malware - DNS Lookup of Ethereum Public RPC Gateways (Smart-Contract C2 Resolver) · unlock with TL Creds
  • SC WordPress Malware - Hidden Administrator Creation and Users-Table Trigger in MySQL Query Log · unlock with TL Creds
  • SC WordPress Malware - Ethereum Public RPC Gateway DNS Resolution (Smart-Contract C2 Dead Drop) · unlock with TL Creds

Indicators of compromise

As of 2026-11-16, Threadlinqs Intelligence tracks 19 indicators of compromise for TL-2026-6157.

19 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

SC is a WordPress malware family named after the 'SC_' markers (e.g. the SC_AUTO_PREPEND constant, sc_-prefixed options and transients) found in injected content. Sucuri (Gabriel Barbosa, published 2026-09-30) found it during incident response and describes it as a 'self-healing mesh': the payload is held in at least eight on-disk locations plus off-disk copies, and a large set of hooks rewrites every other component whenever one is removed. The initial infection vector was not determined by Sucuri or by the secondary reporting; no CVE is tied to this infection chain.

On-disk components documented by Sucuri: (1) .user.ini (also possibly php.ini or .htaccess) setting auto_prepend_file to a shim; (2) a visible shim such as wp-content/c1b12371.php (name varies per site) that includes (3) a hidden dot-prefixed string-table loader, wp-content/.c1b12371.php, which rebuilds the mu-plugin and defines SC_AUTO_PREPEND; (4) wp-content/db.php, a bootstrap drop-in holding the full payload as gzip+base64 that redeploys the plugin when it is missing or too small; (5) wp-content/advanced-cache.php, the earliest drop-in (loaded when WP_CACHE is set), which rebuilds the plugin from five sources and hooks plugins_loaded; (6) a marker-fenced block appended to the active theme's functions.php (observed in theme folder 'khorshidi'); (7) wp-content/mu-plugins/hyper-engine-kit.php; and (8) an identical copy at wp-content/plugins/hyper-engine-kit/hyper-engine-kit.php with a fake settings page, shortcode and activation hook. A ZIP restore bundle with a random hex name may sit in wp-content, uploads or a theme folder, and an encoded stub may sit in the cache directory. Off-disk copies include a randomly named options row holding a gzip/base64 payload (read by advanced-cache.php over a direct DB connection built from the site's credential constants), sc_-prefixed options/transients, a System V shared-memory segment under a fixed numeric key (RAM-resident, possibly owned by another account on shared hosting), cron hooks with randomized names plus a known fetch hook triggered by system cron, and, in related variants, database triggers that recreate an administrator on insert. The payload has no eval and no readable function names, using a string table with a positional substitution cipher.

Backdoor behavior: it filters the plugin list, update transient and site/network plugin views to hide itself (with admin JavaScript as fallback); fingerprints the site (URL/host, WordPress and plugin versions, path hashes, active theme, mu-plugin list, administrator session tokens), encrypts the data and posts it to an endpoint resolved from an Ethereum smart contract read through ~20 public Ethereum RPC gateways (all must be blocked together). Replies may carry front-end JavaScript to inject (e.g. checkout skimming on stores), new PHP to install, and lists of security plugins to deactivate and delete (removal can wipe the plugin directory and reassign/elevate other accounts first). It adopts or creates a hidden administrator, writing directly to users/usermeta tables if the normal API is unavailable, hides the account from user lists, counts and role views, and forges valid authentication cookies so no password is needed. A magic request parameter is handled before WordPress fully loads as a beacon/liveness check.

Monarx (2026-08-17) documented a related SC_-marker variant with additional specifics: SC_DB_BEGIN/SC_DB_END in db.php, SC_ADV_* in advanced-cache.php/object-cache.php, SC_TH_* in theme functions.php, hidden-admin usernames of the form admin_/adm_/administrator_/backup_ plus 6-10 hex characters with an email on the site's own domain, options bu/bp/ic (hidden admin credentials and harvested admin logins), sc_payload_persistent/sc_payload_t options, cron hooks sc_cron_fetch (~10 h) and r1ckj5tjyx1yjm (hourly reinstall), a C2 lookup via eth_call selector 0x3bc5de30 returning an XOR key and C2 URL list, forged ~14-day session cookies, mtime back-dating, a file mtime watermark (mtime % 100000 == 93819), and a browser Service Worker registered under /wp-admin/ and /wp-login.php that captures login POSTs and automates plugin upload/installation. These Monarx specifics are attributed to the Monarx report and may be variant-specific.

Neither source publishes the contract address, RPC gateway hostnames, C2 domains, IP addresses or file hashes, and no actor attribution is given. BeaconBeagle correlation was therefore not applicable (no network IOCs to query). Severity HIGH is analyst-assigned (hidden admin, remote code install, self-healing persistence) and is not stated by the sources. Recommended cleanup order per Sucuri: neutralize the auto_prepend target first (empty it to an inert stub before removing directives, since PHP caches the value up to 300 s), clear off-disk copies (options row, shared memory, sc_ options/transients), remove cron hooks and DB triggers, remove the hidden administrator and orphaned option, remove all files in one pass, then rescan and rotate credentials.

MITRE ATT&CK techniques by tactic:

Defense Evasion

T1027 Obfuscated Files or Information; T1027.013 Encrypted/Encoded File; T1036.005 Match Legitimate Resource Name or Location; T1070.006 Timestomp; T1480 Execution Guardrails; T1564 Hide Artifacts

Persistence

T1053.003 Cron; T1098 Account Manipulation; T1136.001 Local Account; T1505.003 Web Shell

Credential Access

T1056.003 Web Portal Capture

Execution

T1059 Command and Scripting Interpreter; T1059.007 JavaScript

Command and Control

T1071.001 Web Protocols; T1102.001 Dead Drop Resolver; T1573 Encrypted Channel

Discovery

T1082 System Information Discovery

lateral-movement

T1550.004 Web Session Cookie

defense-impairment

T1685 Disable or Modify Tools

Remediation

Patches

  • Keep WordPress core, plugins and themes patched; the initial infection vector was not identified in the sources

Immediate actions

  • Block outbound requests from web servers/PHP-FPM to public Ethereum RPC gateways (all ~20 together, not just the one observed) and alert on eth_call JSON-RPC from the web user
  • Neutralize the auto_prepend_file target first (empty it to an inert stub), then remove the directive from .user.ini, php.ini and .htaccess; do not delete the target while PHP's cache is warm (up to 300 s)
  • Delete the random-name gzip/base64 options row, sc_-prefixed options/transients and malicious cron hooks (e.g. sc_cron_fetch); purge any System V shared-memory segment holding PHP
  • Remove the hidden administrator (capabilities under the default capabilities meta key, absent from the Users screen) and the orphaned option referencing its ID; check information_schema.TRIGGERS for triggers that insert administrators
  • Remove all loaders, shim, both fake hyper-engine-kit copies, the ZIP restore bundle, malicious db.php/advanced-cache.php and the marker-fenced block in the active theme's functions.php in a single pass
  • End all sessions, force password resets and rotate every credential the attacker could have reached (hosting, database, wp-config.php salts)

Workarounds

  • Put the site in maintenance mode / disable PHP and block outbound HTTPS during cleanup
  • Restart PHP-FPM and clear OPcache after removing the loaders

Longer-term hardening

  • Regularly audit wp_options, cron events, database triggers and administrator accounts (including a direct wp_users query vs. the Users screen)
  • Restrict write access to wp-content/mu-plugins, drop-in files and .user.ini; file-integrity monitoring on db.php, advanced-cache.php, object-cache.php and theme functions.php
  • Treat any reappearing file as unfinished cleanup and inspect off-disk sources (DB, shared memory, cron)
  • Deploy a WAF to block exploit attempts, the beacon parameter and outbound C2 traffic; sweep other sites on the same account or server
  • Have admins unregister unexpected Service Workers and clear site data (for the Monarx-documented variant)

Affected and fixed versions

  • WordPress — WordPress sites (core, plugins, themes; PHP hosting with .user.ini/auto_prepend_file support)
    Vulnerable versions: Infected sites; initial infection vector not identified

Timeline

  • Monarx publishes analysis of a WordPress persistence campaign using SC_ markers (SC_DB_*, SC_ADV_*, SC_TH_*), hidden admin accounts and eth_call-based C2 lookups via public Ethereum RPC endpoints.
  • Sucuri (Gabriel Barbosa) publishes 'SC WordPress Malware', describing the self-healing mesh of eight persistence points and a blockchain-controlled backdoor found during incident response in September 2026.
  • The Hacker News notes that the delivery method is unknown and lists typical vectors (unpatched WordPress/plugin/theme flaws, weak credentials, plugin supply-chain attacks, abused upload features); no victim count is published by Sucuri, Monarx or The Hacker News.
  • The Hacker News reports on Sucuri's research ('WordPress Backdoor Rebuilds Itself'); initial infection vector reported as unknown.
  • Defender guidance consolidated across sources: neutralize auto_prepend_file first, clear options row/shared memory/cron/triggers, remove hidden admin, then clean files in one pass and rotate credentials.
  • Daily Security Review reports the ~20 public Ethereum RPC gateway C2 transport, hidden administrator and fake Hyper Engine Kit plugin.
  • RS Web Solutions reports that the backdoor reconstructs itself after cleanup using files, the database and shared memory.
  • SecurityLab (securitylab.ru) reports the self-healing backdoor with eight mutually repairing copies targeting WordPress sites.

Sources cited

Drafted by the Threadlinqs research pipeline from 6 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats