T1059.004
T1059.004 on attack.mitre.org ↗
ATT&CK technique
- PHP web stack: PHP worker built an ALFA-style CGI shell folderSIGXQLT1059.004T1505.003conf 80CVE exploitation, high
Needs a PHP worker as the writer and "cgiapi" in the path or an .alfa extension. A copy renamed without either marker is missed; worker-writes-php and worker-shell cover the rest of the chain.
CVE-2026-102764 · CVE-2026-103849 · CVE-2026-104736 · CVE-2026-109618 · CVE-2026-109619 · CVE-2026-110447 · CVE-2026-111560 · CVE-2026-114625 · CVE-2026-116606 · CVE-2026-119977 · CVE-2026-48356
- PHP web stack: PHP worker spawned a shell or download toolSIGAQLXQLT1059.003T1059.004T1190T1505.003conf 70CVE exploitation
Needs a PHP worker or mod_php Apache as the PARENT and a shell / interpreter / downloader as the child. PHP mail() (sh -c sendmail / msmtp / exim / postdrop) and Apache piped logging (rotatelogs, cronolog) are excluded. The PHP command-line binary is not a parent on purpose (cron jobs and artisan / wp-cli run it all day and it is not reachable from the network). Legitimate exec() calls in an application still match: hunt for a week and baseline them before alerting.
CVE-2026-102764 · CVE-2026-103849 · CVE-2026-104736 · CVE-2026-109618 · CVE-2026-109619 · CVE-2026-110447 · CVE-2026-111560 · CVE-2026-114625 · CVE-2026-116606 · CVE-2026-119977 · CVE-2026-48356
- Node.js stack: Node.js server spawned a shell or download toolSIGAQLXQLT1059.003T1059.004T1190conf 55CVE exploitation
Needs node as the PARENT and a shell / downloader as the child. Children whose command line names npm, npx, yarn, pnpm, git or node-gyp are excluded. Meant for servers: on developer machines it is noise even with the exclusions.
CVE-2023-22621 · CVE-2026-111497 · CVE-2026-126187 · CVE-2026-44267 · CVE-2026-92934
How to deploy
SIGSigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 3
- Promote to an alert once a week of results is clean on your data.
- Check
- The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.
AQLIBM QRadar
- Step 1
- Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
- Step 2
- Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
- Step 3
- For alerting, build the CRE rule from the test stack shown and exclude your known-good building block.
- Check
- Custom properties ("URL Host", "URL", "File Hash", "Process CommandLine") come from your DSMs and content extensions; rename them if yours differ.
XQLCortex XDR
- Step 1
- Paste the XQL into Incident Response > Investigation > Query Builder > XQL Search.
- Step 2
- To alert, save it as a Correlation Rule and set the MITRE tactic and technique printed with the rule.
- Step 3
- Schedule it on the interval you hunt at; keep the fields stage for the alert's columns.
- Check
- CVE rules read PAN-OS URL logs (panw_ngfw_url_raw), which need the NGFW integration and, for HTTPS, decryption.