Which versions of bigmathex are malicious?

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

How do I remediate bigmathex if I installed it?

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

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

Yes — bigmathex is associated with the GHSA-4v7j-fv5q-vv2q, RLMA-2026-01120, RLUA-2026-01889 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 bigmathex 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 bigmathex (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigmathex across your stack and pipelines.

Malicious package

bigmathexnpm

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

MAL-2025-192983

Immediate action

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

npm uninstall bigmathex

What this malware does

The package bigmathex 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)

78d52a55be2e3f5049e8f23cfc7ba78e91116de3cf84b914b0b858d07b2e1ec8

f2d6482202334e84fd3842eee620f23e8bc2b6fbcf1588bbb27c94176cfd0999

5a4cb879f7150a6dbc1cf61f2bb73874b30052b5a0f55163c0828a87af7df52d

9d469cbccffdf57798024bd343b7ec04008cf6afb9c80c14356deb96d5e64fc2

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 bigmathex (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigmathex across your stack and pipelines.
If you installed it — respond
Remove bigmathex 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 bigmathex 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 bigmathex 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. bigmathex 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-4v7j-fv5q-vv2qRLMA-2026-01120RLUA-2026-01889

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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