Which versions of bignumex are malicious?

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

How do I remediate bignumex if I installed it?

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

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

Yes — bignumex is associated with the GHSA-cvwj-6h92-w2cp, RLMA-2025-06068, RLUA-2026-01123, RLUA-2026-01893 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 bignumex 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 bignumex (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bignumex across your stack and pipelines.

Malicious package

bignumexnpm

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

MAL-2025-192574

Immediate action

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

npm uninstall bignumex

What this malware does

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

32884ff132ca375f235dd1d6e843a3178d5777c11127c3f8f155472d2f26a455

c839a719fb3ac340e251cb4eb34af0d9240de8d7e9f13605963617d9e14929b3

275045db8764849b9c0183d000d56de04b464b2a88c9239e87faaa6eed865dd1

f61b10a17a23d1abf0c55b508c3bb07e96f44ed23e268b25f5cd9e2a9ba90ba7

53aeac274d2b6d83f67cc18c97426f42c3d07336196a26b4d0f86f8a13eda905

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

Campaign

GHSA-cvwj-6h92-w2cpRLMA-2025-06068RLUA-2026-01123RLUA-2026-01893

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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