cookie-parser-js (npm) · Malicious Code
Affects cookie-parser-jsSource GCVE Database
Malicious package : remove cookie-parser-js and rotate any secrets on hosts that installed it.
Data as of 12 Jul 2026, 09:18 UTC
Malicious package
Published to npm · OSV MAL-2026-10060
What to do
Remove cookie-parser-js from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmcookie-parser-js | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c6c2bd7c1b5b363e72753401f6edebf816965a625227e6523210e4620ce9bb8a) cookie-parser-js impersonates the widely used cookie-parser package: it copies TJ Holowaychuk / Doug Wilson author metadata, the description, the README (which self-identifies as cookie-parser-ease), and the expressjs repository slug. package.json declares an undocumented runtime dependency `cookie-js-ease` pinned to the mutable tag `latest`, and index.js does `var Cookies = require('cookie-js-ease'); Cookies.set("", "", {expires: 0})` inside the exported cookieParser factory. The Cookies.set call passes empty key/value with expires:0 — a functional no-op whose only effect is to force load and execute the transitive dependency when a consumer requires('cookie-parser-js') and invokes the middleware. `cookie-js-ease` is not a known cookie library and appears fabricated to serve as the payload carrier: because it is pinned to `latest`, its author (controlled by the same actor) can push arbitrary code at any time, giving them code execution inside any consumer application that loads this middleware. The name-similarity to cookie-parser (a top-download express middleware) plus the borrowed identity of its real maintainers is a deliberate confusion attack targeting developers who mistype the package name.
References
- npmjs.com/package/cookie-parser-js/v/1.4.8 (opens in a new tab)
- npmjs.com/package/cookie-parser-js/v/1.4.9 (opens in a new tab)
- npmjs.com/package/cookie-parser-js/v/1.5.0 (opens in a new tab)
- npmjs.com/package/cookie-parser-js/v/1.0.8 (opens in a new tab)
- npmjs.com/package/cookie-parser-js/v/1.5.3 (opens in a new tab)
- npmjs.com/package/cookie-parser-js/v/1.5.2 (opens in a new tab)
- npmjs.com/package/cookie-parser-js/v/1.5.1 (opens in a new tab)