Which versions of cookie-parser-js are malicious?

The following npm versions of cookie-parser-js are flagged malicious: 1.0.8, 1.4.8, 1.4.9, 1.5.0. Treat any of these as compromised.

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

cookie-parser-js is a typosquat — you almost certainly intended a legitimately-named package. Remove cookie-parser-js, 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-js — how do I know if it already compromised me?

If cookie-parser-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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

Yes — cookie-parser-js is associated with the IN-MAL-2026-009299, IN-MAL-2026-009295, IN-MAL-2026-009298, IN-MAL-2026-009297 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-js across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cookie-parser-js (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cookie-parser-js across your stack and pipelines.

Malicious package

cookie-parser-jsnpm

Malicious code in cookie-parser-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10060

Immediate action

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

npm uninstall cookie-parser-js

What this malware does

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.

Malicious versions

4 flagged

1.0.81.4.81.4.91.5.0

Indicators of compromise (SHA-256)

17fefe6ee6bd8b2724a609aee2957f0d486e3a497f8df274acd6267fd10cda4e

4286341b29814d2b1c35a1107d2097f2a66f11784da088b99a9bffc4b58d4814

8f5cbe73e97166cefb452a32b6d70349d19dd5f06b7ef11ae8af64fac38e79cd

c6c2bd7c1b5b363e72753401f6edebf816965a625227e6523210e4620ce9bb8a

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cookie-parser-js (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cookie-parser-js across your stack and pipelines.
If you installed it — respond
cookie-parser-js is a typosquat — you almost certainly intended a legitimately-named package. Remove cookie-parser-js, 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-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks cookie-parser-js before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. cookie-parser-js on npm has been identified as a malicious package (versions 1.0.8, 1.4.8, 1.4.9, 1.5.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009299IN-MAL-2026-009295IN-MAL-2026-009298IN-MAL-2026-009297

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cookie-parser-js-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