Threat reportMalwareTL-2026-0385
Joomla SEO Spam Injector — Obfuscated PHP Backdoor Hijacking Site Visitors (php.spam-seo.joomla-injector.002)
Active mass-compromise campaign against outdated Joomla (<5.X) installations deploys a heavily obfuscated PHP loader at the top of index.php. On every page load the backdoor exfiltrates $_SERVER data to C2 cdn.erpsaz.com (primary) or cdn.saholerp.com (fallback) and selects one of three cloaking modes — silent visitor redirect, raw HTML injection, or fake XML-sitemap / HTML served to search crawlers — enabling large-scale SEO poisoning, visitor hijacking, and reputation damage.
Key facts
| Identifiers | TL-2026-0385 |
|---|---|
| Also known as | Joomla SEO Spam Injector, Joomla Obfuscated PHP Backdoor, php.spam-seo.joomla-injector.002, erpsaz Joomla Injector, saholerp Joomla Loader |
| Severity | HIGH |
| CVSS | 8.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L) |
| Affected products | Joomla! Joomla Core; Joomla! Extensions Directory (JED) Third-party Joomla extensions |
| Weaknesses (CWE) | CWE-506, CWE-94, CWE-601, CWE-434, CWE-912 |
| Malware | joomla-seo-spam-injector, php.spam-seo.joomla-injector.002 |
| Tools | curl_exec (PHP libcurl binding) |
| MITRE ATT&CK techniques | T1008 Fallback Channels, T1027 Obfuscated Files or Information, T1036 Masquerading, T1059 Command and Scripting Interpreter, T1071 Application Layer Protocol, T1082 System Information Discovery, T1102 Web Service, T1132 Data Encoding, T1140 Deobfuscate/Decode Files or Information, T1189 Drive-by Compromise, T1190 Exploit Public-Facing Application, T1491 Defacement and 6 more in the attack flow |
| Motivation | FINANCIAL |
| Target sectors | small-business, ecommerce, media, education, nonprofit, hospitality, professional-services |
| Target regions | Global, North America, Europe, Latin America, Asia-Pacific |
| Detection rules | 9 (1 shown free) |
| Sources | 15 cited sources |
Detection coverage
As of 2026-04-17, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0385 across Splunk SPL, Microsoft KQL and Sigma, covering 28 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: Joomla index.php Modified With Fragmented Two-Char Concat + Tilde-Delimited Base64 Table — Exploitation Phase
Detects the initial exploitation / injection artifact of the Joomla SEO Spam Injector (php.spam-seo.joomla-injector.002). Correlates file-integrity-monitor writes to a Joomla document-root index.php with content matching the fragmented two-character string concatenation (e.g. 'BASE6' . '4_dec' . 'ODE') and/or the tilde-delimited base64 lookup table used by wffn()/mpjy(). Fires when either obfuscation marker appears inside a freshly modified index.php.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1505.003, T1027.010, T1027.013, T1190
- Data sources: ossec, wazuh, tripwire, file_integrity_monitoring, auditd, microsoft_defender_for_endpoint
- Severity: high
- Confidence: high
Splunk SPL
index=fim sourcetype IN ("ossec:alerts","wazuh:alerts","tripwire:events") earliest=-24h (file_path="*index.php" OR dest_file="*index.php" OR path="*index.php") action IN ("modified","changed","created")
| rex field=_raw "(?<frag_pattern>'[A-Za-z0-9_]{4,6}'\s*\.\s*'[A-Za-z0-9_]{2,5}'\s*\.\s*'[A-Za-z0-9_]{2,5}')"
| rex field=_raw "(?<tilde_table>(?:[A-Za-z0-9+/=]{8,}~){10,}[A-Za-z0-9+/=]{8,})"
| where isnotnull(frag_pattern) OR isnotnull(tilde_table)
| eval obfuscation_signal=case(isnotnull(frag_pattern) AND isnotnull(tilde_table),"both",isnotnull(frag_pattern),"fragmented_concat",isnotnull(tilde_table),"tilde_base64_table")
| stats values(obfuscation_signal) as signals values(file_path) as files values(user) as users count by host
| where count>0
| table _time host files users signals countMicrosoft KQL
union isfuzzy=true DeviceFileEvents, SecurityEvent
| where TimeGenerated > ago(24h)
| where (FileName == "index.php" or FolderPath endswith "\\index.php" or FolderPath endswith "/index.php")
| where ActionType in ("FileModified","FileCreated","FileRenamed") or EventID in (4663,4656)
| extend FragConcat = extract(@"'[A-Za-z0-9_]{4,6}'\s*\.\s*'[A-Za-z0-9_]{2,5}'\s*\.\s*'[A-Za-z0-9_]{2,5}'", 0, tostring(AdditionalFields))
| extend TildeTable = extract(@"(?:[A-Za-z0-9+/=]{8,}~){10,}[A-Za-z0-9+/=]{8,}", 0, tostring(AdditionalFields))
| where isnotempty(FragConcat) or isnotempty(TildeTable)
| project TimeGenerated, DeviceName, FolderPath, FileName, InitiatingProcessAccountName, FragConcat, TildeTable
| summarize Hits=count(), Samples=make_set(FolderPath, 5) by DeviceName, InitiatingProcessAccountNameSigma
title: Joomla index.php Contains Joomla SEO Spam Injector Obfuscation Markers
id: a0385001-0001-4e3a-9a30-joomla-injector-fim
status: experimental
description: Detects the exploitation artifact of TL-2026-0385 (php.spam-seo.joomla-injector.002) — a Joomla document-root index.php containing fragmented two-character string concatenations that rebuild base64_decode/curl_exec/explode at runtime, and/or a tilde-delimited base64 blob of approximately 27 segments.
references:
- https://blog.sucuri.net/2026/04/joomla-seo-spam-injector-obfuscated-php-backdoor-hijacking-site-visitors.html
- https://labs.sucuri.net/signatures/malwares/php-spam-seo-joomla-injector-002/
- https://attack.mitre.org/techniques/T1505/003/
- https://attack.mitre.org/techniques/T1027/010/
- https://attack.mitre.org/techniques/T1027/013/
author: Threadlinqs Team
date: 2026-04-17
tags:
- attack.persistence
- attack.defense_evasion
- attack.t1505.003
- attack.t1027.010
- attack.t1027.013
logsource:
product: linux
service: auditd
category: file_event
detection:
selection_path:
name|endswith: '/index.php'
selection_frag_concat:
content|re: "'[A-Za-z0-9_]{4,6}'\\s*\\.\\s*'[A-Za-z0-9_]{2,5}'\\s*\\.\\s*'[A-Za-z0-9_]{2,5}'"
selection_tilde_table:
content|re: '([A-Za-z0-9+/=]{8,}~){10,}[A-Za-z0-9+/=]{8,}'
condition: selection_path and (selection_frag_concat or selection_tilde_table)
falsepositives:
- Legitimate obfuscators or licensing wrappers that emit similar token fragmentation (rare in Joomla core)
- Minified third-party PHP libraries that happen to contain long tilde-delimited base64 strings
level: highTuning notes: Scope file-integrity feeds to Joomla document roots only. If a deployment pipeline routinely modifies index.php, exclude the deployment service account and its source IP. Raise threshold to require BOTH fragmented_concat AND tilde_base64_table co-occurring in the same file for lower-noise environments.
- Defender/Azure File Event on Joomla index.php With Obfuscator Signature — Exploitation Phase · unlock with TL Creds
- Webserver PHP Process Spawns curl Sibling or Issues Outbound /[indicator] GET — Post-Exploitation Phase · unlock with TL Creds
- Endpoint DNS or Network Connection to erpsaz/saholerp/lashowroom Infrastructure — C2 Phase · unlock with TL Creds
- Sigma — Joomla SEO Spam Injector Obfuscated Loader in index.php (Exploitation Phase) · unlock with TL Creds
- Sigma — PHP Worker Issues Outbound /[indicator]?ua= Fingerprint GET (Post-Exploitation Phase) · unlock with TL Creds
- Sigma — DNS / Proxy Egress to erpsaz, saholerp, lashowroom, or Known C2 IPs (C2 Phase) · unlock with TL Creds
- PHP Worker Outbound GET to /[indicator] With Base64 ua= Fingerprint — Post-Exploitation Phase · unlock with TL Creds
- DNS or HTTP Egress to Joomla SEO Spam Injector C2 Infrastructure — C2 Phase · unlock with TL Creds
Indicators of compromise
As of 2026-04-17, Threadlinqs Intelligence tracks 28 indicators of compromise for TL-2026-0385.
Sample indicators (3 of 28)
- IP address:
91.239.78[.]37 - Domain:
lashowroom[.]com - IP address:
195.26.86[.]16
Defanged, TLP:CLEAR. Full set of 28 indicators: unlock with TL Creds.
Technical analysis
TL-2026-0385 tracks an active Joomla compromise campaign documented by Sucuri on 2026-04-16 (Puja Srivastava). The attacker injects a small, heavily obfuscated PHP loader at the very top of the target site's index.php. The loader is structured across four functions — wffn() (bootstrap decoder), mpjy() (27-entry string lookup table), fotr() (traffic cop / cloaking engine), and joog() (HTTP requester and exfiltrator). All sensitive strings (function names explode, base64_decode, curl_exec, domain fragments, URL components, header names) are fragmented into two-character concatenations (for example 'BASE6' . '4_dec' . 'ODE') and/or stored as a tilde-delimited base64 blob decoded into a 27-index lookup table — defeating naive signature scanners that search for literal sinks or complete base64 strings.
On every page load the backdoor serializes data from the PHP $_SERVER superglobal (HTTP_HOST, REQUEST_URI, HTTP_USER_AGENT, REMOTE_ADDR, etc.), base64-encodes it, and issues a curl_exec() GET to http://cdn.erpsaz.com/admin.php?ua=<encoded_fingerprint>. If the primary returns an empty/non-200 response, the loader retries exactly once against http://cdn.saholerp.com/admin.php (a second flag prevents infinite recursion). A third domain, lashowroom.com, is fully decoded at index 25 of the string table but is never referenced by any URL-constructing index call — present as a decoy to waste analyst time.
The fotr() function then branches on the C2 response: (Mode 1) if the body starts with 'http' the loader issues header('Location: ' . $body) and exit()s, silently redirecting the visitor to an attacker-chosen URL; (Mode 2) if the body starts with '##', the prefix is stripped via substr($body, 2) and the remainder is echoed directly into the page, injecting arbitrary spam HTML (e.g. the spam product links reported by the original victim); (Mode 3) if the response length exceeds 90 characters and contains '</urlset>' the loader sets Content-type:text/xml and returns the body as a fake XML sitemap, otherwise if the body contains '<html' it serves the raw HTML — both modes designed to cloak responses to search-engine crawlers and inject keyword-stuffed pages for SEO poisoning.
Because all directives are delivered remotely and the local file footprint is a single obfuscated block, defenders often miss the infection during casual inspection. The same site can be redirecting end users one hour and feeding Google a fake sitemap the next — fully controlled by the C2 operator. This dynamic control makes the infection long-lived and hard to correlate with any one visible symptom. Root cause in every Sucuri case studied has been exploitation of known, patched vulnerabilities in Joomla core or third-party extensions on installations running branches older than 5.X (which is end-of-life).
C2 infrastructure resolves to 91.239.78.37 (AS6698 VIRTUALSYSTEMS, RIPE, Poland/Ukraine) for cdn.erpsaz.com and 195.26.86.16 (AS43641 SOLLUTIUM-NL, RIPE, Ukraine/Poland) for cdn.saholerp.com. Both parent zones (erpsaz.com, saholerp.com) use Cloudflare nameservers, masking origin at the DNS layer but revealing authoritative zones directly on the sub-CDN hostnames. Sucuri tracks the family under signature php.spam-seo.joomla-injector.002 (original signature lineage dates to 2019; this 2026 variant is the first with the fragmented-string + tilde-delimited-table obfuscation pattern).
Impact is financial and reputational: compromised domains push traffic and link equity to attacker-promoted products, search engines demote or de-index cloaked pages, browsers may flag the site via Safe Browsing, and ad fraud downstream is common. The backdoor does not itself include the spam content — it is a pure remote loader, so removal requires deleting the injected block from index.php, resetting all admin credentials, and completing a full integrity scan of every PHP file on the host to locate any secondary implants.
MITRE ATT&CK techniques by tactic:
Command and Control
T1008 Fallback Channels; T1071 Application Layer Protocol; T1102 Web Service; T1132 Data Encoding; T1568 Dynamic Resolution
Defense Evasion
T1027 Obfuscated Files or Information; T1036 Masquerading; T1140 Deobfuscate/Decode Files or Information
Execution
T1059 Command and Scripting Interpreter
Discovery
T1082 System Information Discovery
Initial Access
T1189 Drive-by Compromise; T1190 Exploit Public-Facing Application
Impact
T1491 Defacement; T1496 Resource Hijacking
Persistence
T1505 Server Software Component
Resource Development
T1583 Acquire Infrastructure; T1608 Stage Capabilities
Reconnaissance
Remediation
Patches
- Upgrade Joomla core to the latest 5.X release
- Apply the latest security updates for every installed Joomla extension
- Upgrade PHP to a supported branch (8.2+)
Immediate actions
- Remove the obfuscated PHP block injected at the top of Joomla index.php and any cloned copies across the document root
- Block outbound DNS/HTTP to cdn.erpsaz.com, cdn.saholerp.com, and lashowroom.com at the perimeter and web-server egress
- Block outbound connections to 91.239.78.37 and 195.26.86.16 at the firewall
- Force rotate all Joomla administrator credentials, database passwords, FTP/SFTP keys, and hosting control-panel logins
- Invalidate all active Joomla sessions and regenerate session-secret configuration values
- Run a full file-integrity scan of every .php file on the host to locate secondary backdoors, uploaders, or dropped shells
- Submit the domain for re-review in Google Search Console once cleaned to begin reversing de-indexing
Workarounds
- If immediate upgrade is not possible, place the /administrator directory behind HTTP basic auth or IP allow-list
- Enable Joomla's built-in reCAPTCHA on the admin login form
- Disable PHP functions not required by Joomla (exec, shell_exec, system, passthru) via disable_functions in php.ini
- Block outbound egress from the web server except for explicit allow-listed update endpoints
Longer-term hardening
- Upgrade Joomla to the currently supported 5.X branch — all 3.X and 4.X branches are end-of-life and silently missing security patches
- Deploy a web application firewall (Sucuri, Cloudflare, ModSecurity + CRS) with virtual patching for known Joomla CVEs and outbound C2 egress filtering
- Enable Joomla two-factor authentication for every administrator account and restrict /administrator by IP allow-list
- Set file permissions baseline: directories 755, PHP files 644, never world-writable
- Audit all installed Joomla extensions monthly; remove unused, abandoned, or untrusted extensions
- Deploy host-based file-integrity monitoring (OSSEC, Wazuh, Tripwire) on the document root with alert on any change to index.php, configuration.php, or template files
- Route all outbound traffic from the web tier through an egress proxy and alert on any GET to URIs ending in /admin.php to unknown CDN-named subdomains
Affected and fixed versions
- Joomla! — Joomla Core
Vulnerable versions: 3.X (EOL); 4.X (EOL); any pre-5.X installation
Fixed in: 5.X current branch (only via upgrade, not patch) - Joomla! Extensions Directory (JED) — Third-party Joomla extensions
Vulnerable versions: any unpatched extension with known CVE used as initial access vector
Fixed in: latest vendor-released version of each installed extension
Timeline
- Sucuri Labs publishes signature php.spam-seo.joomla-injector.002, first generation of the Joomla SEO spam injector family.
- New 2026 variant observed in Sucuri incident response queue, introducing two-character fragmented function names and the 27-entry tilde-delimited base64 lookup table as primary obfuscation technique.
- Joomla site owner reports suspicious product links appearing on their ecommerce pages that were never added to the catalog; pages serve different content to search crawlers than to browsers.
- Sucuri Security Analyst Puja Srivastava begins deobfuscation of the injected PHP loader; identifies four-function architecture (wffn, mpjy, fotr, joog) and multi-mode cloaking logic.
- C2 infrastructure confirmed: locked-ioc-5 (primary, locked-ioc-10 / AS6698), locked-ioc-4 (fallback, locked-ioc-11 / AS43641); locked-ioc-6 identified as decoy string never used in URL construction.
- Sucuri publishes full technical writeup of the Joomla SEO Spam Injector campaign on blog.sucuri.net, including IOCs, cloaking modes, and remediation steps.
- Threadlinqs Intelligence publishes TL-2026-0385 with full MITRE mapping, expanded IOC set, and detection rules (SPL, KQL, Sigma) derived from the Sucuri signature lineage.
- As of 2026-05-29, this Sucuri-documented Joomla SEO-spam injector campaign remains an active concern: outdated pre-5.X Joomla sites are still being mass-compromised in 2026 (e.g. SEO-spam via actively-exploited Astroid CVE-2026-21628) and no takedown, sinkhole, or arrest has hit its erpsaz/saholerp C2. Specific C2 domains are expected to rotate, so the exact infra may go quiet, but the technique and remote-loader family stay live.
Sources cited
- Joomla! Security Announcements developer.joomla.org · Advisory · 2026-04-16
- Sucuri Blog: Joomla SEO Spam Injector — Obfuscated PHP Backdoor Hijacking Site Visitors blog.sucuri.net · Vendor report · 2026-04-16
- Sucuri Labs Signature: php.spam-seo.joomla-injector.002 labs.sucuri.net · Vendor report · 2019-04-02
- Joomla! 5.X Downloads and Upgrade Information joomla.org · Vendor report · 2026-04-16
- MITRE ATT&CK: Server Software Component — Web Shell (T1505.003) MITRE · Research · 2026-01-01
- MITRE ATT&CK: Obfuscated Files or Information — Encrypted/Encoded File (T1027.013) MITRE · Research · 2026-01-01
- MITRE ATT&CK: Obfuscated Files or Information — Command Obfuscation (T1027.010) MITRE · Research · 2026-01-01
- MITRE ATT&CK: Application Layer Protocol — Web Protocols (T1071.001) MITRE · Research · 2026-01-01
- MITRE ATT&CK: Data Encoding — Standard Encoding (T1132.001) MITRE · Research · 2026-01-01
- MITRE ATT&CK: Resource Hijacking (T1496) MITRE · Research · 2026-01-01
- MITRE ATT&CK: Exploit Public-Facing Application (T1190) MITRE · Research · 2026-01-01
- CWE-506: Embedded Malicious Code MITRE · Research · 2026-01-01
- CWE-94: Improper Control of Generation of Code (Code Injection) MITRE · Research · 2026-01-01
- CWE-601: URL Redirection to Untrusted Site ('Open Redirect') MITRE · Research · 2026-01-01
- Google Search Central: Hacked sites — cloaking developers.google.com · Vendor report · 2026-01-01
Previous and next in malware
Drafted by the Threadlinqs research pipeline from 15 sources; published ; last updated —.