Malware in string-tools-be6c
The npm package string-tools-be6c contained malware that provided full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- string-tools-be6c
The npm package string-tools-be6c was found to contain malware. According to the GitHub advisory, any computer that has 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 computer. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning there is no guarantee that removing the package will remove all malicious software resulting from the installation.\n\nThis represents a critical supply chain attack through a malicious npm package with full system compromise capabilities.
Indicators of compromise
- Packages
- string-tools-be6c
Remediation
- Immediately isolate any computer that has string-tools-be6c installed from the network
- Rotate all secrets, API keys, credentials, and cryptographic keys from a different, uncompromised computer
- Remove the string-tools-be6c package from affected systems
- Perform a full forensic analysis and malware scan on affected systems
- Review system logs and access patterns for signs of unauthorized activity during the period the package was installed
- Consider full system reimaging if compromise is suspected
Sources
- GitHub Advisory GHSA-93cp-5ff7-p9m5 · GitHub Advisory Database
Cite this entry
"Malware in string-tools-be6c." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 18, 2026; last updated June 20, 2026. https://supplychainattack.org/incident/malware-in-string-tools-be6c-1v0u7x
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package