Malware in ts-numbering
Malware discovered in the npm package ts-numbering. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with ts-numbering installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ts-numbering
The npm package ts-numbering has been identified as containing malware. According to the GitHub advisory (GHSA-fvpj-9j2j-grmr), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated 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 represents a critical supply chain attack through a compromised package in the npm ecosystem.
Indicators of compromise
- Packages
- ts-numbering
Remediation
- Immediately isolate any system with ts-numbering installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the ts-numbering package from all affected systems
- Conduct a full security audit and malware scan of 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 the compromise
Sources
- GitHub Advisory GHSA-fvpj-9j2j-grmr · GitHub Advisory Database
Cite this entry
"Malware in ts-numbering." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-ts-numbering-15r5tc
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