Malware in knip-bun
The npm package knip-bun was found to contain malware, resulting in full system compromise for any computer with the package installed or running. All secrets and keys should be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with knip-bun installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- knip-bunnpm package containing malware
The npm package knip-bun was identified as containing malware. According to the GitHub Advisory (GHSA-xrrj-hrq9-xvxg), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised computer. 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 initial compromise, as the attacker may have gained full control of the system.\n\nThis is a critical supply chain incident affecting the npm ecosystem.
Indicators of compromise
- Packages
- knip-bun
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the knip-bun package from all affected systems
- Conduct a full security audit of any system that had knip-bun installed
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
- Monitor for any unauthorized access or lateral movement from affected systems
Sources
- GitHub Advisory GHSA-xrrj-hrq9-xvxg · GitHub Advisory Database
Cite this entry
"Malware in knip-bun." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malware-in-knip-bun-1wa6gb
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 typescirpt-cli (npm)
The npm package typescirpt-cli (a typosquat of typescript-cli) contained malicious code in its postinstall script that downloads and executes a binary (main.exe) on Windows and WSL systems, and exfiltrates system metadata to a hardcoded IP address.
npmTyposquattingCompromised package - containedcritical
Malicious code in typescipt-core (npm)
The npm package typescipt-core (a typosquat of typescript) contained malicious postinstall code that downloads and executes a second-stage payload on Windows and WSL systems. The dropper exfiltrates host profile information to 193.70.34.101:20099 before fetching attacker-controlled executables.
npmCompromised packageTyposquatting - containedcritical
Malicious code in typesript-cli (npm)
The npm package 'typesript-cli' (a one-character typosquat of 'typescript') contains malicious code in its postinstall script that downloads and executes a Windows PE binary, and can cross the Linux/WSL sandbox boundary to execute payloads on the Windows host. The script also beacons to a hardcoded IP endpoint.
npmTyposquattingCompromised package - resolvedcritical
Malicious code in @mohamed_nowisar/depconf-canary-test (npm)
The npm package @mohamed_nowisar/depconf-canary-test contained malicious code in its preinstall hook that automatically collected and exfiltrated host and CI environment information to an attacker-controlled webhook endpoint without user consent.
npmCompromised package