AlienVault OTX pulse data confirms active in-the-wild exploitation of two leaked PHP core remote code execution vulnerabilities — CVE-2026-109618 and CVE-2026-109619 (both CVSS v4.0 9.2 Critical) — with automated scanning infrastructure attributed to Mirai-variant IoT botnet operators. The pre-patch leak of technical details gave adversaries a measurable head start: scanning commenced approximately 20 minutes after the official patch release on October 21, 2026, compressing the defender patching window to near zero and effectively weaponizing the disclosure timeline itself.
Targeted sectors are Retail, Financial Services, and Technology, with observed victimology concentrated in the United States, Germany, Singapore, and the United Kingdom. The campaign specifically hunts WooCommerce and Magento deployments — platforms that sit directly on payment flows and customer PII, making this both a server-compromise and a cardholder-data event.
Threat Summary
The pulse documents a classic vulnerability-race monetization pattern: exploit code or sufficient technical detail for two PHP core memory-corruption flaws leaked before coordinated disclosure, and criminal infrastructure was staged in advance of patch availability.
The attack chain is notably low-friction:
- Reconnaissance — Internet-wide scanning (Shodan/Censys-derived target lists plus botnet-driven sweeps) for PHP versions in the vulnerable range, fingerprinted via headers, error pages, and known eCommerce URL paths (
/wp-admin,/checkout, Magento/adminroutes). - Initial Access (T1190 — Exploit Public-Facing Application) — Unauthenticated requests abusing PHP's
session.upload_progressmechanism combined with malformedmultipart/form-databoundaries to trigger out-of-memory corruption in PHP core, yielding code execution in the web server process context. - Execution (T1059.004 — Unix Shell / T1059.003) — Post-exploitation payloads observed in open directories (
PHP2Shellwebshell droppers) spawn reverse shells and pull second-stage binaries from distribution nodes. - Botnet Assimilation — Mirai-variant tags on the pulse indicate compromised Linux/IoT-adjacent hosts are recruited as scanning and DDoS capacity; compromised web servers are likely monetized separately (access brokerage, skimmer injection on Magento/WooCommerce checkouts).
The strategic objective appears dual-track: (a) bulk recruitment of vulnerable infrastructure into an IoT/scanner botnet, and (b) selective hands-on exploitation of eCommerce targets for payment data theft and access resale. The presence of deliberately juvenile/opsec-poor scanner hostnames (godofthunder.st, gettingheadfromduckysmom.st) alongside a more structured C2 hostname (maste.mangsud.org) is consistent with low-to-mid sophistication criminal operators leveraging leaked exploit tooling rather than a disciplined APT.
Threat Actor / Malware Profile
Attribution: Unknown actor cluster. Behavioral overlap with Mirai-derivative botnet operations (fast mass-scan onset, disposable .st TLD infrastructure, open-directory payload staging). No credible nation-state linkage is indicated by the pulse.
PHP2Shell Webshell (post-exploitation tooling):
- Distribution method: Delivered in the same request stream as the multipart/form-data exploit, or fetched second-stage from open directories indexed by the hunt.io research. Payloads frequently staged in world-readable directories (
/tmp,/var/tmp,/dev/shm) and dropped into webroot as randomized.phpfilenames. - Payload behavior: Minimal eval/`` shell wrappers, often with a client-supplied parameter gate (e.g.,
?cmd=,?pass=) and base64-obfuscated function dispatch. Observed variants enumerate running processes, query/etc/passwd, and curl/wget out to C2 for Mirai-variant binaries (ELFarchitecture-specific droppers: x86, ARM, MIPS). - C2 communication: Outbound HTTP/HTTPS to scanner/distribution nodes including
godofthunder.st,gettingheadfromduckysmom.st, andmaste.mangsud.org. Mirai-variant stage-2 traffic uses the classic raw-TCP botnet protocol with hardcoded XOR keys; the HTTP tier is used for payload delivery and victim check-in. - Persistence mechanism: Cron entries under the web server user (
www-data,nginx,apache), webshell redundancy (multiple droppers across webroot), and — on hosts where the web user has elevated rights — systemd user services or modified.bashrc/rc.local. - Anti-analysis techniques: Base64/gzinflate-wrapped PHP, randomized filenames and parameter keys, User-Agent filtering (serving 404s to non-attacker clients), time-bombed self-deletion of loader scripts, and payload staging in memory-only filesystems (
/dev/shm) to evade disk forensics.
MITRE ATT&CK mapping: T1190 (Exploit Public-Facing Application), T1059 (Command and Scripting Interpreter), T1505.003 (Web Shell), T1053.003 (Cron), T1027 (Obfuscated Files or Information), T1071.001 (Web Protocols), T1583.001 (Acquire Infrastructure: Domains).
IOC Analysis
The pulse's seven indicators split into two operational classes:
| Type | Indicators | SOC Operationalization |
|---|---|---|
| CVE | CVE-2026-109618, CVE-2026-109619 (primary); CVE-2025-55182, CVE-2025-32975 (adjacent exposure surfaced in scan tooling) | Drive asset inventory reconciliation — every internet-facing PHP host must be version-mapped and patched. These are not blocklist IOCs; they are exposure queries. |
| Domain / Hostname | godofthunder.st, gettingheadfromduckysmom.st, maste.mangsud.org | Block at DNS resolver, egress proxy, and EDR network layer. Hunt retroactively for 30+ days of DNS/proxy telemetry — resolution of any of these from a server segment (not just endpoints) is a high-fidelity compromise signal. |
Tooling guidance:
- DNS/proxy logs (Corelight/Zeek, Palo Alto, Squid, Umbrella) for domain retro-hunt.
- Vulnerability scanners (Tenable, Qualys, Wazuh) authenticated against PHP version strings to validate CVE-2026-109618/109619 exposure — note that banner-only checks will miss backported builds.
- EDR (CrowdStrike, MDE, SentinelOne) for process-lineage detection: a web server process spawning shells is the highest-signal behavioral indicator and requires no IOC dependency.
- Web server access logs — grep for abnormally large
multipart/form-dataPOST bodies,session.upload_progresskeys in POST data, and POSTs to URIs that do not normally accept uploads.
The .st TLD (São Tomé) disposable infrastructure should be treated as ephemeral: block the domains today, but weight your detections toward the behavioral layer (exploit request shape and post-exploit process lineage), which survives infrastructure rotation.
Detection Engineering
---
title: PHP2Shell Exploitation - Multipart Form-Data RCE Attempt Against PHP (CVE-2026-109618 / CVE-2026-109619)
id: 7f3a1c2e-9b4d-4e1a-a6c8-202611210001
status: production
description: Detects web server access log patterns consistent with exploitation of PHP core OOB memory corruption via malformed multipart/form-data combined with session.upload_progress abuse. High volume or oversized multipart POSTs to non-upload endpoints are a strong pre-compromise signal.
author: Security Arsenal Threat Intelligence
logsource:
category: webserver
detection:
selection_upload_progress:
- cs-uri-query|contains: 'PHP_SESSION_UPLOAD_PROGRESS'
- cs-method: 'POST'
selection_multipart:
c-content-type|contains: 'multipart/form-data'
selection_abnormal:
sc-bytes|gt: 2000000
condition: selection_multipart and (selection_upload_progress or selection_abnormal)
falsepositives:
- Legitimate large file upload workflows on dedicated upload endpoints
level: high
tags:
- attack.initial_access
- attack.t1190
- cve.2026.109618
- cve.2026.109619
date: 2026/11/21
---
title: Web Server Process Spawning Shell - PHP2Shell Post-Exploitation
id: 7f3a1c2e-9b4d-4e1a-a6c8-202611210002
status: production
description: Detects web server or PHP-FPM worker processes spawning interactive shells or download utilities — the canonical post-exploitation lineage of the PHP2Shell campaign pulling Mirai-variant second stages.
author: Security Arsenal Threat Intelligence
logsource:
category: process_creation
product: linux
detection:
selection_parent:
ParentImage|endswith:
- '/php-fpm'
- '/php'
- '/apache2'
- '/httpd'
- '/nginx'
- '/litespeed'
selection_child:
Image|endswith:
- '/sh'
- '/bash'
- '/dash'
- '/curl'
- '/wget'
- '/nc'
- '/ncat'
- '/python'
- '/perl'
condition: selection_parent and selection_child
falsepositives:
- Legitimate application backup or image-processing pipelines invoking system utilities
- Monitoring agents executed via cron under the web user
level: critical
tags:
- attack.execution
- attack.t1059.004
- attack.t1505.003
date: 2026/11/21
---
title: PHP2Shell / Mirai-Variant C2 DNS Resolution
description: Detects DNS queries to disposable scanner and C2 infrastructure identified in OTX pulse for the PHP2Shell campaign. Resolution from server VLANs indicates active compromise; resolution from endpoints indicates redirect/drive-by exposure.
id: 7f3a1c2e-9b4d-4e1a-a6c8-202611210003
status: production
author: Security Arsenal Threat Intelligence
logsource:
category: dns
detection:
selection:
query|contains:
- 'godofthunder.st'
- 'gettingheadfromduckysmom.st'
- 'maste.mangsud.org'
condition: selection
falsepositives:
- Threat research sandbox detonation
level: critical
tags:
- attack.command_and_control
- attack.t1071.001
date: 2026/11/21
// PHP2Shell Campaign Hunt — Microsoft Sentinel
// Hunts C2 DNS resolution, suspicious web-server process lineage, and exploit-shaped outbound connections
let C2Domains = dynamic(["godofthunder.st", "gettingheadfromduckysmom.st", "maste.mangsud.org"]);
let Lookback = 30d;
// Stage 1: DNS resolution of campaign infrastructure
let DnsHits = DeviceNetworkEvents
| where TimeGenerated > ago(Lookback)
| where RemoteUrl has_any (C2Domains)
| project DnsTime = TimeGenerated, DeviceName, RemoteUrl, RemoteIP, InitiatingProcessFileName, InitiatingProcessCommandLine;
DnsHits;
// Stage 2: Web server / PHP process spawning shells or downloaders
DeviceProcessEvents
| where TimeGenerated > ago(Lookback)
| where InitiatingProcessFileName has_any ("php-fpm", "php", "apache2", "httpd", "nginx", "w3wp.exe")
or InitiatingProcessCommandLine has_any ("php-fpm", "apache", "nginx")
| where FileName in~ ("sh", "bash", "dash", "curl", "wget", "nc", "ncat", "python", "perl", "powershell.exe", "cmd.exe")
| project ProcTime = TimeGenerated, DeviceName, InitiatingProcessFileName, FileName, ProcessCommandLine, ProcessId
| order by ProcTime desc;
// Stage 3: Outbound connections FROM web processes to rare/external IPs (post-exploit beacons)
DeviceNetworkEvents
| where TimeGenerated > ago(Lookback)
| where InitiatingProcessFileName has_any ("php-fpm", "php", "apache2", "httpd", "nginx")
| where RemoteIPType == "Public"
| summarize ConnectionCount = count(), RemoteIPs = make_set(RemoteIP, 20) by DeviceName, InitiatingProcessFileName
| where ConnectionCount < 50 // low-volume egress from a web process is anomalous
| order by ConnectionCount asc;
#!/usr/bin/env bash
# PHP2Shell / CVE-2026-109618 / CVE-2026-109619 — Linux Web Server Hunt Script
# Run on suspected web hosts. Read-only. Outputs findings to /tmp/php2shell_hunt_<timestamp>.log
TS=$(date +%Y%m%d_%H%M%S)
LOG="/tmp/php2shell_hunt_${TS}.log"
echo "=== PHP2Shell Hunt — $(hostname) — ${TS} ===" | tee "$LOG"
# 1. PHP version exposure check
{
echo "[+] PHP version check (vulnerable range per CVE-2026-109618/109619):"
php -v 2>/dev/null || echo " php binary not found in PATH"
dpkg -l 2>/dev/null | grep -i php || rpm -qa 2>/dev/null | grep -i php
} | tee -a "$LOG"
# 2. Webshell droppers in webroot and temp dirs (recent + suspicious patterns)
{
echo "[+] Suspicious PHP files (modified last 45 days, webroot + tmp):"
find /var/www /srv/www /tmp /var/tmp /dev/shm -type f -name "*.php" -mtime -45 2>/dev/null
echo "[+] Eval/base64/gzinflate signatures:"
grep -rlE "eval\s*\(|gzinflate|base64_decode\s*\(|shell_exec|passthru|\$_GET\[.*\]\s*\(" \
/var/www /srv/www /tmp /var/tmp /dev/shm 2>/dev/null | head -50
} | tee -a "$LOG"
# 3. Persistence: cron under web users
{
echo "[+] Cron persistence for web users:"
for u in www-data nginx apache nobody; do
echo "--- $u ---"
crontab -u "$u" -l 2>/dev/null
done
ls -la /etc/cron.d/ /var/spool/cron/ 2>/dev/null
echo "[+] Suspicious systemd units referencing /tmp or /dev/shm:"
grep -rlE "/tmp/|/dev/shm/" /etc/systemd/system/ 2>/dev/null
} | tee -a "$LOG"
# 4. Network: active connections and C2 resolution attempts
{
echo "[+] Active outbound connections from web processes:"
ss -tnp 2>/dev/null | grep -E "php|apache|nginx|httpd"
echo "[+] C2 domain resolution test (NXDOMAIN expected if sinkholed/blocked):"
for d in godofthunder.st gettingheadfromduckysmom.st maste.mangsud.org; do
getent hosts "$d" && echo "!!! RESOLVED: $d — investigate immediately"
done
} | tee -a "$LOG"
# 5. Access log exploitation signatures
{
echo "[+] Exploit-shaped requests in access logs (upload_progress / oversized multipart):"
grep -sE "PHP_SESSION_UPLOAD_PROGRESS|multipart/form-data" /var/log/apache2/access*.log /var/log/nginx/access*.log 2>/dev/null | tail -100
} | tee -a "$LOG"
echo "=== Hunt complete. Review $LOG ===" | tee -a "$LOG"
Response Priorities
Immediate (0–4 hours):
- Block
godofthunder.st,gettingheadfromduckysmom.st, andmaste.mangsud.orgat DNS resolver, egress proxy, and EDR network controls; alert on any historical resolution. - Deploy the Sigma process-lineage rule fleet-wide — web processes spawning shells is near-zero false positive and catches compromise regardless of exploit variant.
- Inventory every internet-facing PHP runtime; emergency-patch to the October 21, 2026 fixed builds. If patching is blocked, apply WAF virtual-patching rules rejecting
multipart/form-databodies containingPHP_SESSION_UPLOAD_PROGRESSon non-upload routes.
24 hours:
- Retro-hunt 30+ days of DNS, proxy, and access logs for C2 resolution and exploit-shaped requests; treat any server-segment DNS hit as confirmed compromise and isolate.
- For any compromised eCommerce host (WooCommerce/Magento): force rotation of all administrative credentials, database credentials, API keys, and payment-gateway secrets; audit admin account creation and checkout template modifications for skimmer injection.
- Validate integrity of
php.ini, session handler configuration, and webroot file trees against known-good baselines.
1 week:
- Move PHP applications behind a WAF with virtual patching capability and enforce network segmentation so web servers cannot initiate arbitrary outbound connections (egress allow-listing breaks both reverse shells and Mirai stage-2 retrieval).
- Eliminate direct internet exposure of PHP-FPM and admin panels; enforce FIM (file integrity monitoring) on webroots.
- Establish a rapid-patch SLA for CVSS 9.0+ pre-disclosure-leak events — this campaign proved the exploit-to-patch gap can be measured in minutes, not days. Subscribe to OTX pulse feeds for early warning on disclosure-timeline anomalies.
Related Resources
Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.