Malware in ts-biginteger-lib
Malware was discovered in the npm package ts-biginteger-lib. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with ts-biginteger-lib installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ts-biginteger-lib
A critical malware incident was identified in the npm package ts-biginteger-lib. According to the GitHub Advisory (GHSA-6v6m-rhh8-ww9v), any computer with this package installed or running should be considered fully compromised.
The advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.
This represents a supply chain compromise through a malicious package distribution in the npm ecosystem.
Indicators of compromise
- Packages
- ts-biginteger-lib
Remediation
- Immediately isolate any computer with ts-biginteger-lib installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the ts-biginteger-lib package from all affected systems
- Perform a full security audit and malware scan of affected systems
- Review system logs for any unauthorized access or activity
- Consider full system reimaging if compromise is confirmed
- Audit all systems that may have been accessed from compromised machines
Sources
- GitHub Advisory GHSA-6v6m-rhh8-ww9v · GitHub Advisory Database
Cite this entry
"Malware in ts-biginteger-lib." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-ts-biginteger-lib-iw20d1
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit