accounts-ddos-shieldnpm
accounts-ddos-shield is a confirmed malicious npm package (MAL-2026-12132) that typosquats a legitimate package to trick installs (malicious versions 0.0.2, 33.3.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in accounts-ddos-shield (npm)
What this malware does
On require of the package, helpers.js selects a platform-specific payload path and downloads an opaque binary from one of several Cloudflare Workers hosts whose names are assembled from split string fragments via Array.join to hide the destinations from static inspection (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS TXT reassembly fallback under tin/tina/ldr/win.dl.well1.site. The fetched bytes are written to /var/tmp or %TEMP% under decoy names impersonating Microsoft diagnostics (dotnet_diag<hex>.exe,.cache_<hex>,.analytics_state), chmod 0755 on POSIX, and spawned detached via /bin/sh or cmd.exe start. The module is labeled _helpers.js with telemetry-framing comments while it stages and executes a remote binary. The package name presents as a DDoS-protection utility, but no such functionality is delivered — the sole effect of loading the module is to run attacker-controlled code on the installer's host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for accounts-ddos-shield (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging accounts-ddos-shield across your stack and pipelines.
If you installed it — respond
accounts-ddos-shield is a typosquat — you almost certainly intended a legitimately-named package. Remove accounts-ddos-shield, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If accounts-ddos-shield was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks accounts-ddos-shield before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks accounts-ddos-shield-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.