Suspicious Miasma npm Credential Exfiltration via Google API Client User Agent (via proxy)

PremiumReviewedSigma · Medium · v1
Category
proxy
Author
HuntRule
Published
2026-11-05
Updated
2026-11-05

ATT&CK techniques

Cred Access → Exfiltration
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Impact

What it detects

This rule detects the exact Google API Node.js client user agent string used by the Miasma supply-chain payload in the @redhat-cloud-services npm compromise to exfiltrate harvested developer and cloud credentials. Matching this specific version triplet where Google client libraries are not expected suggests the obfuscated index.js exfiltration routine has run.

Related detections9 linkedT1567 — drag to rearrange
Suspicious Python-Requests Exfiltration to Webhook.site (s1ngularity Aftermath)
Malicious Network Sniffing of Pod Identity Endpoint via tcpdump
Suspicious Helm Tiller Unauthenticated Access on Port 44134
Malicious prt-scan Campaign Exfiltration Script prt_exfil.sh (via file_event)
Malicious TeamPCP durabletask C2 git-service and m-kosche (via dns_query)
Malicious Mini Shai-Hulud SAP npm Telemetry Exfiltration C2 (via dns_query)
Suspicious AWS API Activity From WinSCP Client User-Agent
Malicious MOVEit Transfer Web Shell X-siLock-Comment Header (via webserver)
Suspicious Discord Webhook Exfiltration via HTTP (via proxy)
Suspicious Miasma npm Credential Exfiltration via Google API Client User Agent (via proxy)
Pivot detection · T1567 · 9 related

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