Malware in commonjs-assert
Malware discovered in the npm package commonjs-assert. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- commonjs-assert
The npm package commonjs-assert has been identified as containing malware. According to the GitHub Advisory (GHSA-hcmm-fvc7-pjv3), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. 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 compromise.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem, with potential for complete system compromise on any machine where it was installed or executed.
Indicators of compromise
- Packages
- commonjs-assert
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the commonjs-assert package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Review system logs for suspicious activity during the period the package was installed
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
- Check for any unauthorized access or lateral movement from affected systems
Sources
- GitHub Advisory GHSA-hcmm-fvc7-pjv3 · GitHub Advisory Database
Cite this entry
"Malware in commonjs-assert." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 10, 2026; last updated August 10, 2026. https://supplychainattack.org/incident/malware-in-commonjs-assert-1l9839
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 autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting