Malware in cors-version
Malware was discovered in the npm package cors-version. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from unaffected systems.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- cors-versionnpm package
A malicious version of the npm package cors-version was identified and published to the npm registry. The package contains malware that provides attackers with full control of any system on which it is installed or running.\n\nAny computer with this package installed should be considered fully compromised. All secrets, keys, and credentials stored on affected systems must be rotated immediately from a different, unaffected computer.\n\nWhile the package should be removed, complete removal of all malicious artifacts cannot be guaranteed due to the level of system access granted to the attacker. A full security audit and potential system rebuild may be necessary for affected systems.\n\nThe advisory was published on GitHub on 2026-08-04 under GHSA-2hwp-7m6r-hgjg.
Indicators of compromise
- Packages
- cors-version
Remediation
- Immediately remove the cors-version package from all systems
- Rotate all secrets, keys, and credentials from a clean, unaffected computer
- Audit system logs for signs of unauthorized access or data exfiltration
- Consider full system rebuild or forensic analysis for critical systems
- Check npm audit logs and dependency trees to identify all affected systems
- Monitor for any suspicious activity on systems that had the package installed
Sources
- GitHub Advisory GHSA-2hwp-7m6r-hgjg · GitHub Advisory Database
Cite this entry
"Malware in cors-version." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-cors-version-lljcgw
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 sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package