NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

accounts-ddos-shieldnpm

Advisory published Updated

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)

MAL-2026-12132
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall accounts-ddos-shield

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

2 flagged
0.0.233.3.8

Indicators of compromise (SHA-256)

343cd6e6bdb885bf8fe4d59b376a32c5ab57f309707c4253b2bf7307d631be79
3bd79f6fb6188c1b18eb067e515747ea24c328e491275e52c83910da1e44d71b

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for accounts-ddos-shield (2 malicious versions).

  2. 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.

  3. Did it already run?

    If accounts-ddos-shield was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. accounts-ddos-shield on npm has been identified as a malicious package (versions 0.0.2, 33.3.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014549IN-MAL-2026-014558

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.

Explore

accounts-ddos-shield (npm) malicious package — MAL-2026-12132 | O3 Security