Malicious code in hwi-lib (npm)
The npm package hwi-lib version 1.0.1 was identified as malicious by the OpenSSF Package Analysis project. The package contains code that communicates with a domain associated with malicious activity.
- Disclosed
- Last updated
- Blast radius
- All users of hwi-lib version 1.0.1 on npm
- Ecosystems
- Attack vectors
- Affected entities
- hwi-lib · 1.0.1
The OpenSSF Package Analysis project identified hwi-lib version 1.0.1 on npm as containing malicious code. The malicious behavior was detected through analysis of the package's communication patterns.
The package communicates with a domain associated with malicious activity, indicating potential data exfiltration, command-and-control communication, or other malicious intent. This represents a direct compromise of the package itself rather than an account takeover or build system compromise.
The incident was disclosed on August 5, 2026, and tracked under OpenSSF malicious package identifier MAL-2026-12067. Users of this specific version should immediately remove the package and audit their systems for any unauthorized activity.
Indicators of compromise
- Packages
- hwi-lib@1.0.1
Remediation
- Immediately uninstall hwi-lib version 1.0.1 from all affected systems
- Audit systems that installed this package for signs of compromise or unauthorized access
- Check npm audit logs and package.json lock files to identify all installations
- Review network logs for connections to the malicious domain associated with this package
- Consider using alternative packages for the functionality previously provided by hwi-lib
- Update to a safe version if one becomes available, or use a verified alternative package
Sources
- GitHub Advisory GHSA-f9r2-8m6r-p3qv · GitHub Advisory Database
Cite this entry
"Malicious code in hwi-lib (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-hwi-lib-npm-1i6di8
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 svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package