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

big-numernpm

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

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

What this malware does

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

Indicators of compromise (SHA-256)

d33c6d4bf0076dbf6ad1f01662441a53e90d5df9d6c7fd1f14359161f5a0fe08

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 big-numer (version 5.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging big-numer across your stack and pipelines.

  2. If you installed it — respond

    Remove big-numer 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 big-numer 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 big-numer 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. big-numer on npm has been identified as a malicious package (version 5.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j5jp-xc7m-26vm

References

Detect & block this

O3 blocks big-numer-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.

Malware detection Runtime egress monitoring