DNS queries to known malicious C2 domains from axios/plain-crypto-js npm compromise indicators

Alerts on DNS queries to known malicious C2 domains tied to an Axios npm supply-chain compromise.

FreeReviewedSigma · High · v5
Category
dns
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2026-04-01
Updated
2026-07-31

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule flags DNS traffic where endpoints attempt to resolve specific domains identified as command-and-control infrastructure tied to the axios/plain-crypto-js npm supply chain compromise. Attackers rely on resolving these domains to establish outbound communication for follow-on payload behavior. The detection relies on DNS query telemetry matching the configured suspicious domain names.

Related detections9 linkedT1071.001 — drag to rearrange
Malicious HarborWatch RAT Command and Control Beacon by User Agent (via proxy)
Suspicious UAT-10608 Credential Harvesting C2 Beacon via HTTP
Malicious BadIIS C2 Communication via lwxatisme User-Agent
Possible PS1Bot C2 Beacon With Drive Serial URI Pattern (via proxy)
Suspicious WarmCookie C2 Beacon With Fixed Firefox User-Agent
Malicious Renamed Python Interpreter Executing nvidia.py RAT
Malicious Self-Signed TLS Certificate With Exploit Subject via Zeek X509
Suspicious Network Connection From wabmig.exe (Turian Injection)
Suspicious wmicodegen.dll Sideload by inetinfo.exe (UAT-8099 Cobalt Strike)
DNS queries to known malicious C2 domains from axios/plain-crypto-js npm compromise indicators
Pivot detection · T1071.001 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.