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
- resolvedcritical
Malicious code in santana-baileys (npm)
Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.
npmCompromised package - resolvedcritical
Malicious code in elephant-tusk-runner (npm)
The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.
npmCompromised package - resolvedcritical
Malicious code in @cats-cdf/browser-metrics-meter (npm)
The npm package @cats-cdf/browser-metrics-meter contained malicious code in its preinstall lifecycle script that exfiltrated system reconnaissance data (username, hostname, public IP) to an OAST collector domain. The package executed this behavior unconditionally on installation without consent or documented purpose.
npmCompromised package - resolvedcritical
Malicious code in @ks-video/kwai-player-web (npm)
The npm package @ks-video/kwai-player-web contained malicious code in its postinstall hook that exfiltrated system reconnaissance data (hostname, username, working directory, network interfaces, environment variable names) over plain HTTP to an unrelated third-party domain. The package has no legitimate relationship to the declared publisher Kwai/@ks-video.
npmCompromised package