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

npm-doc-buildnpm

Malicious code in npm-doc-build (npm) Remove it immediately and rotate any exposed credentials.

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

What this malware does

The package npm-doc-build was found to contain malicious code.

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

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

de3094bb10170209a4225724c5cc0934cbc551bbcf01dd6f6df0205ca158ee6a
2529276a3738febefbf8612a0a43ee94944a3631b3adce06ec650b859d14d424
e02a5339e3c7017ad72be2bb9ed62f13b6d4aeef3450ada18af95a6203e8e105
3cb9f1961355fcc49289afd923d188b1555a60abbcfba750bd0a8a594c39ab79

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove npm-doc-build from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If npm-doc-build 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 npm-doc-build 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. npm-doc-build on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r89p-9949-2qj7RLMA-2026-01465RLUA-2026-01801

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks npm-doc-build-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.

npm-doc-build (npm) malicious package — MAL-2026-1360 | O3 Security