Malware in ts-bn-proto
Malware was discovered in the npm package ts-bn-proto. 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 ts-bn-proto installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ts-bn-proto
A malware incident was identified in the npm package ts-bn-proto, published on GitHub advisories (GHSA-wxpc-r4jx-9jrw). The advisory indicates that any computer with this package installed or running should be considered fully compromised.\n\nAccording to the advisory, all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. The package should be removed, though the advisory notes that full control of the computer may have been granted to an outside entity, meaning removal of the package alone may not eliminate all malicious software introduced by the installation.\n\nThis represents a critical supply chain compromise affecting npm ecosystem users who installed or ran this package.
Indicators of compromise
- Packages
- ts-bn-proto
Remediation
- Immediately rotate all secrets and keys stored on affected computers from a different, uncompromised system
- Remove the ts-bn-proto package from all affected systems
- Conduct a full security audit of any system that had ts-bn-proto installed, as complete removal of malicious software may not be guaranteed
- Review system logs and network activity for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the compromise is suspected to be severe
Sources
- GitHub Advisory GHSA-wxpc-r4jx-9jrw · GitHub Advisory Database
Cite this entry
"Malware in ts-bn-proto." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 29, 2026; last updated July 29, 2026. https://supplychainattack.org/incident/malware-in-ts-bn-proto-a8j0e9
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 sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package