Which versions of bignumx are malicious?

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

How do I remediate bignumx if I installed it?

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

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

Yes — bignumx is associated with the GHSA-fqx6-v425-9qwr, RLMA-2025-06069, RLUA-2026-01124, RLUA-2026-01894 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 bignumx 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 bignumx (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bignumx across your stack and pipelines.

Malicious package

bignumxnpm

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

MAL-2025-191541

Immediate action

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

npm uninstall bignumx

What this malware does

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

98b45b53c91ebee4c77ebf3ba359608318ce17878eb8edb1cbd2a7e65238dbff

745b8508e8818e81e53f71cf2467fa31620191825b820f424eb9f86ab1e5f49e

8b117f0b214640b5bafc20e8b0ce654032e064717bfa1d3c10655f3e25a15953

3e29635ac3939e718ed7308fe0a856d66a37274eca98b8d0bc90abb2fdc68592

6969741131cd597a7a6c5bb61b27e3ff10bec49d8e293cdbd28e323e4dce6574

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

Campaign

GHSA-fqx6-v425-9qwrRLMA-2025-06069RLUA-2026-01124RLUA-2026-01894

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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