Which versions of cookie-parser-es are malicious?

The following npm versions of cookie-parser-es are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate cookie-parser-es if I installed it?

cookie-parser-es is a typosquat — you almost certainly intended a legitimately-named package. Remove cookie-parser-es, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed cookie-parser-es — how do I know if it already compromised me?

If cookie-parser-es was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is cookie-parser-es part of a known attack campaign?

Yes — cookie-parser-es is associated with the IN-MAL-2026-009296 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find cookie-parser-es across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cookie-parser-es (version 1.0.7).

Malicious package

cookie-parser-esnpm

Advisory published Jul 9, 2026Updated Jul 9, 2026

cookie-parser-es is a confirmed malicious npm package (MAL-2026-10059) that typosquats a legitimate package to trick installs (malicious version 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cookie-parser-es (npm)

MAL-2026-10059

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall cookie-parser-es

What this malware does

Package name and metadata impersonate the widely-used cookie-parser middleware: README, API surface, and package.json author (TJ Holowaychuk <[email protected]>) and repository (expressjs/js-cookie-parser) are copied from the legitimate package, with an additional contributor [email protected] appended. The factory in index.js lines 39-41 calls var Cookies = require('cookie-ease'); Cookies.set("", "", {expires: 0}) — cookie-ease is NOT declared in dependencies and is loaded/executed the moment a consumer wires the middleware following the README's app.use(cookieParser()) example. A second related package set-cookie-ease is declared in dependencies pinned to "latest" (mutable), allowing the maintainer to swap the executed payload after registry scans pass. The combination of name confusion against a top-100 npm package, identity impersonation of a well-known author, runtime loading of an undeclared sister package, and a mutable latest pin matches the standard typosquat-dropper supply-chain attack shape.

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

b33910f1e874310521f231a698952504d94e6fbdb08ef9d43e02ee220afc18b1

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for cookie-parser-es (version 1.0.7).
If you installed it — respond
cookie-parser-es is a typosquat — you almost certainly intended a legitimately-named package. Remove cookie-parser-es, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If cookie-parser-es was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. cookie-parser-es on npm has been identified as a malicious package (version 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009296

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cookie-parser-es-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database