Which versions of bigmathix are malicious?

The following npm versions of bigmathix are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0. Treat any of these as compromised.

How do I remediate bigmathix if I installed it?

Remove bigmathix 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 bigmathix — how do I know if it already compromised me?

If bigmathix 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 bigmathix part of a known attack campaign?

Yes — bigmathix is associated with the GHSA-fvcx-rrjg-gr82, RLMA-2026-01121, RLUA-2026-01890 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 bigmathix 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 bigmathix (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigmathix across your stack and pipelines.

Malicious package

bigmathixnpm

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

MAL-2026-831

Immediate action

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

npm uninstall bigmathix

What this malware does

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

11 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.1.0

Indicators of compromise (SHA-256)

5fce43c0e03186c2441c8a54be7cb130625459fe9179665e242f223f0c7d2944

b200be57a4cdb466d56397968f69dd3845955ced56c5229608dbf03762106ff9

bbd7c2fb336743838dc62b128fa1887a8fe18313e640478af78224aa379a0c95

c427e0b7cabc87725d45114282f59e7499cceafb15b6ba5c0bed3dffcfd8648b

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 bigmathix (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigmathix across your stack and pipelines.
If you installed it — respond
Remove bigmathix 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 bigmathix 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 bigmathix 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. bigmathix on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fvcx-rrjg-gr82RLMA-2026-01121RLUA-2026-01890

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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