Malware in st-biginteger
Malware discovered in the npm package st-biginteger. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with st-biginteger installed or running
- Ecosystems
- Attack vectors
- Affected entities
- st-biginteger
The npm package st-biginteger has been identified as containing malware. According to the GitHub Advisory (GHSA-2652-pqcw-rfg5), 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 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 is a critical supply chain incident affecting the npm ecosystem, with potential for widespread impact across all systems that have installed or executed this package.
Indicators of compromise
- Packages
- st-biginteger
Remediation
- Immediately isolate any system with st-biginteger installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the st-biginteger package from all affected systems
- Perform a full security audit and malware scan on all affected systems
- Review system logs for any suspicious activity or unauthorized access
- Consider full system reimaging if compromise is confirmed
- Notify all users and systems that may have been affected by this package
Sources
- GitHub Advisory GHSA-2652-pqcw-rfg5 · GitHub Advisory Database
Cite this entry
"Malware in st-biginteger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-st-biginteger-19qj66
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting