Malware in sjs-biginteger
Malware was discovered in the npm package sjs-biginteger. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with the malicious package installed
- Ecosystems
- Attack vectors
- Affected entities
- sjs-bigintegernpm package
The npm package sjs-biginteger was found to contain malware. According to the GitHub advisory (GHSA-38ww-f26r-f8w7), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the malicious package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThis incident was disclosed on 2026-07-06 via the GitHub advisory system.
Indicators of compromise
- Packages
- sjs-biginteger
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the sjs-biginteger package from all affected systems
- Audit system logs for unauthorized access or activity
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
- Check for any other suspicious packages or modifications on affected systems
Sources
- GitHub Advisory GHSA-38ww-f26r-f8w7 · GitHub Advisory Database
Cite this entry
"Malware in sjs-biginteger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-sjs-biginteger-1m079u
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