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

webpackbootstrap5npm

Advisory published Updated

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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
5.0.0

Indicators of compromise (SHA-256)

9e94c2a29fdc72c1f02612cbc0ecc1ca548a00fb34a8913c11f818a7da7e79de

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for webpackbootstrap5 (version 5.0.0).

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

Campaign

GHSA-2q27-vrr7-584g

References

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