Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

webpackbootstrap5npm

webpackbootstrap5 is a confirmed malicious npm package (MAL-2026-16201) that typosquats a legitimate package to trick installs (malicious version 5.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in webpackbootstrap5 (npm)

MAL-2026-16201
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall webpackbootstrap5

What this malware does

[email protected] typosquats bootstrap and ships a disguised in-browser proxy kit. Its bundled loader (index-z2b7r4.js) XOR-decodes a list of endpoints with a fixed key and injects remote scripts from https://dyingefforlessefforlessours.com via document.head.appendChild, then boots a Scramjet/wisp WebSocket proxy that routes page traffic through operator-controlled relays. The loader matches (same sha256) sibling packages webpackbootstrapscripts and @zaka13/thing by the same publisher (zaka13). Harm is browser-side when the asset is served; no install script runs.

Malicious versions

1 flagged
5.0.0

Detection & response playbook

Typosquat
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for webpackbootstrap5 (version 5.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging webpackbootstrap5 across your stack and pipelines.

  2. If you installed it — respond

    webpackbootstrap5 is a typosquat — you almost certainly intended a legitimately-named package. Remove webpackbootstrap5, 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 webpackbootstrap5 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.

  4. How O3 protects you

    O3 blocks webpackbootstrap5 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

No. webpackbootstrap5 on npm has been identified as a malicious package (version 5.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • pkgwarden · finder

Detect & block this

O3 blocks webpackbootstrap5-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

webpackbootstrap5 (npm) malicious package — MAL-2026-16201 | O3 Security