Which versions of bigmathlib are malicious?

The following npm versions of bigmathlib are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate bigmathlib if I installed it?

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

I already installed bigmathlib — how do I know if it already compromised me?

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

Is bigmathlib part of a known attack campaign?

Yes — bigmathlib is associated with the GHSA-5mv4-pjx6-7x42, RLMA-2026-01122, RLUA-2026-01891 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bigmathlib across my projects, lockfiles, and CI pipelines?

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

Malicious package

bigmathlibnpm

Malicious code in bigmathlib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192598

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bigmathlib

What this malware does

The package bigmathlib 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

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

d73c91abd6a323d119e598928fc613100786424177806e36bb5ebd15f666de3e

29e535ed570f999285684c4f2a79ce262d460a98329790e34f433542070b9298

157806e0ddbbb53441e47fc94c975c21dbfd2c007f59408a9b536388a062054e

2f6ae20d092678f9f19505b07e8281838985707de89e59b85ab9312967e0b5e5

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigmathlib (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigmathlib across your stack and pipelines.
If you installed it — respond
Remove bigmathlib 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.
Did it already run?
If bigmathlib 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.
How O3 protects you
O3 blocks bigmathlib 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. bigmathlib on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5mv4-pjx6-7x42RLMA-2026-01122RLUA-2026-01891

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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