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

jacob-zumanpm

Advisory published Updated

jacob-zuma is a confirmed malicious npm package (MAL-2025-190974) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jacob-zuma (npm)

MAL-2025-190974
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall jacob-zuma

What this malware does

The package jacob-zuma 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged
1.0.11.0.2

Indicators of compromise (SHA-256)

0aae0c8157adb8caf2d0af0aab7f402560e4489ff1f7f8b615bb7f79a23b3c1e
b5046cda17d3d1de49e402cc9dbb860de629a5843d6ad27d2db95f626a280408
addfd2b4ed6626370e9abd197380adb534dfcf60747fe7d73ab72bda54a93878

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for jacob-zuma (2 malicious versions).

  2. If you installed it — respond

    jacob-zuma is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

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

Campaign

GHSA-7cqw-82xh-p6qp

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks jacob-zuma-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

jacob-zuma (npm) malicious package — MAL-2025-190974 | O3 Security