Malware in chlklib
Malware was discovered in the npm package chlklib, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with chlklib installed or running
- Ecosystems
- Attack vectors
- Affected entities
- chlklib
The npm package chlklib was found to contain malware. According to the GitHub Advisory (GHSA-pw26-7j7h-jhf5), 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, unaffected 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, given that the attacker may have gained full control of the system.\n\nThe advisory was published on 2026-08-18 via GitHub's advisory database.
Indicators of compromise
- Packages
- chlklib
Remediation
- Immediately rotate all secrets and keys stored on affected computers from a different, unaffected computer
- Remove the chlklib package from all systems
- Conduct a full security audit of any system that had chlklib installed
- Consider the affected system(s) fully compromised and plan for complete rebuild if critical infrastructure
- Review access logs and monitor for unauthorized activity on affected systems
Sources
- GitHub Advisory GHSA-pw26-7j7h-jhf5 · GitHub Advisory Database
Cite this entry
"Malware in chlklib." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malware-in-chlklib-6v3d97
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