Malicious code in vexium-kit (npm)
The npm package vexium-kit contained malicious code that executed remote JavaScript on installation, fetching and executing operator-controlled payloads with access to Node.js internals. The package declared dependencies on browser credential-theft tools, indicating intent to steal Chromium passwords and cookies from infected systems.
- Disclosed
- Last updated
- Blast radius
- All npm installations of vexium-kit prior to removal
- Ecosystems
- Attack vectors
- Affected entities
- vexium-kitnpm package containing malicious code
The npm package vexium-kit was published with embedded malicious code in its index.js file. On require, the package issued an HTTPS request to a hardcoded IP endpoint (31.97.137.157:45000/icons/116) and executed the response's credits field as JavaScript using new Function(), granting the remote operator access to Node.js require, process, and Buffer capabilities.\n\nThe package was advertised as a zero-dependency utility toolkit but declared dependencies on @primno/dpapi, better-sqlite3, sqlite3, and node-machine-id—tools commonly used to decrypt Chromium DPAPI-protected credentials and extract browser login databases. This indicates the operator-supplied payload was designed to steal browser passwords and cookies from infected systems.\n\nThe malicious code included an unused setDefaultModule decoy function referencing font-awesome CDN paths, suggesting obfuscation tactics. The package was identified by Amazon Inspector and reported to the OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- vexium-kit
- IPs
- 31.97.137.157
Remediation
- Immediately uninstall vexium-kit from all systems
- Audit npm install logs to identify when vexium-kit was installed
- Assume any system that installed vexium-kit has been compromised; reset Chromium browser passwords and review login history
- Review browser credential stores (Chrome, Edge, Brave) for unauthorized access
- Monitor for outbound HTTPS connections to 31.97.137.157:45000 in network logs
- Update npm dependencies and audit the dependency tree for other suspicious packages
- Consider using npm audit and supply chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-wxpv-6v7m-pcp9 · GitHub Advisory Database
Cite this entry
"Malicious code in vexium-kit (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malicious-code-in-vexium-kit-npm-17nn9k
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 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.
npmCompromised package - resolvedcritical
Malware in alphazone
The npm package alphazone contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in chai-as-deployer
Malware was discovered in the npm package chai-as-deployer, 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 - containedcritical
Malware in checkout-common-tokens
Malware was discovered in the npm package checkout-common-tokens. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package