Malicious code in clx-cookieparser (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (29b7ab13cd76393ea58b540ccf13b4ab4660edb4fac210d86a67e51b45fa1d0c) Package ships a verbatim copy of the Express 'cookie-parser' middleware under a different name ('clx-cookieparser') and declares a repository field 'expressjs/clx-cookieparser' that does not exist under the expressjs GitHub organization, suggesting unauthorized association with the upstream project. The shipped code (index.js requires 'cookie' and 'cookie-signature' and re-implements cookie-parser) contains no network I/O, no install/lifecycle scripts, no obfuscation, and no credential handling — there is no demonstrated installer-side harm. The concern is name/metadata confusion: a developer searching for or mistyping 'cookie-parser' could install this lookalike, and the false repository attribution amplifies the confusion. Routing to human review so a maintainer can assess intent (benign mirror vs. squat positioning) and registry action. ## Source: ghsa-malware (2fe4e10a5059e10daab1da62d3a625251bd2a87d1570966423f7ee26c49fff47) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The clx-cookieparser npm package is a malicious package that impersonates the Express 'cookie-parser' middleware by shipping identical code under a misleading name and false repository metadata. While the code itself does not demonstrate installer-side harm such as network activity or credential theft, the package's presence is considered a critical compromise indicator. The malicious package may lead to full system compromise, requiring secret and key rotation from a clean environment. This is a case of a malicious package masquerading as a legitimate one to trick developers into installing it. There is no vendor patch or official fix since this is a malicious package rather than a vulnerability in a legitimate product.
Potential Impact
Systems with the clx-cookieparser package installed should be considered fully compromised. All secrets and keys stored on the affected system must be rotated immediately from a different, trusted system. Removal of the package alone does not guarantee full remediation, as the attacker may have established persistent control or installed additional malware. There is no evidence of installer-side harm in the package code itself, but the risk arises from the malicious intent and potential post-install compromise.
Mitigation Recommendations
Remove the clx-cookieparser package immediately if installed. Rotate all secrets, credentials, and keys from a separate, trusted system. Conduct a thorough security review of the affected system for signs of compromise or persistence. Since this is a malicious package impersonating a legitimate one, avoid installing packages with suspicious or misleading metadata. No official patch or fix exists because this is not a vulnerability in legitimate software but a malicious package. Monitor trusted sources and registries for updates or takedown actions regarding this package.
Malicious code in clx-cookieparser (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (29b7ab13cd76393ea58b540ccf13b4ab4660edb4fac210d86a67e51b45fa1d0c) Package ships a verbatim copy of the Express 'cookie-parser' middleware under a different name ('clx-cookieparser') and declares a repository field 'expressjs/clx-cookieparser' that does not exist under the expressjs GitHub organization, suggesting unauthorized association with the upstream project. The shipped code (index.js requires 'cookie' and 'cookie-signature' and re-implements cookie-parser) contains no network I/O, no install/lifecycle scripts, no obfuscation, and no credential handling — there is no demonstrated installer-side harm. The concern is name/metadata confusion: a developer searching for or mistyping 'cookie-parser' could install this lookalike, and the false repository attribution amplifies the confusion. Routing to human review so a maintainer can assess intent (benign mirror vs. squat positioning) and registry action. ## Source: ghsa-malware (2fe4e10a5059e10daab1da62d3a625251bd2a87d1570966423f7ee26c49fff47) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The clx-cookieparser npm package is a malicious package that impersonates the Express 'cookie-parser' middleware by shipping identical code under a misleading name and false repository metadata. While the code itself does not demonstrate installer-side harm such as network activity or credential theft, the package's presence is considered a critical compromise indicator. The malicious package may lead to full system compromise, requiring secret and key rotation from a clean environment. This is a case of a malicious package masquerading as a legitimate one to trick developers into installing it. There is no vendor patch or official fix since this is a malicious package rather than a vulnerability in a legitimate product.
Potential Impact
Systems with the clx-cookieparser package installed should be considered fully compromised. All secrets and keys stored on the affected system must be rotated immediately from a different, trusted system. Removal of the package alone does not guarantee full remediation, as the attacker may have established persistent control or installed additional malware. There is no evidence of installer-side harm in the package code itself, but the risk arises from the malicious intent and potential post-install compromise.
Mitigation Recommendations
Remove the clx-cookieparser package immediately if installed. Rotate all secrets, credentials, and keys from a separate, trusted system. Conduct a thorough security review of the affected system for signs of compromise or persistence. Since this is a malicious package impersonating a legitimate one, avoid installing packages with suspicious or misleading metadata. No official patch or fix exists because this is not a vulnerability in legitimate software but a malicious package. Monitor trusted sources and registries for updates or takedown actions regarding this package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6661
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-jpg2-3r22-63v7"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a42ed4b27e9c79719935d2d
Added to database: 06/29/2026, 22:10:19 UTC
Last enriched: 07/09/2026, 10:50:26 UTC
Last updated: 07/31/2026, 10:23:09 UTC
Views: 302
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.