Which versions of bignumberx are malicious?

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

How do I remediate bignumberx if I installed it?

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

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

Yes — bignumberx is associated with the RLMA-2025-06067, RLUA-2026-01892 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 bignumberx 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 bignumberx (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 bignumberx across your stack and pipelines.

Malicious package

bignumberxnpm

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

MAL-2025-192714

Immediate action

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

npm uninstall bignumberx

What this malware does

The package bignumberx was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

764a60640d3d5b16a94d7f5124868bf66f8b1b81dd614c3f754b6bcc5d05e304

373a71b85072c46f30d8c905a20be254d540302a332c6cae5663cb76e4b8b620

42aac9cfcc2bcd03a22309ba2aaccf1ebfdc6ac93df52f7fd946a482391c309d

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 bignumberx (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 bignumberx across your stack and pipelines.
If you installed it — respond
Remove bignumberx 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 bignumberx 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 bignumberx 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. bignumberx 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

RLMA-2025-06067RLUA-2026-01892

References

reversinglabs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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