Which versions of cookie-validate are malicious?

The following npm versions of cookie-validate are flagged malicious: 2.2.4. Treat any of these as compromised.

How do I remediate cookie-validate if I installed it?

Remove cookie-validate from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If cookie-validate 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-validate part of a known attack campaign?

Yes — cookie-validate is associated with the RLMA-2025-05708, RLUA-2025-06102, RLUA-2026-01224 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-validate across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cookie-validate (version 2.2.4).

Malicious package

cookie-validatenpm

Advisory published Dec 1, 2025Updated Mar 19, 2026

cookie-validate is a confirmed malicious npm package (MAL-2025-191569) that executes malicious code on install (malicious version 2.2.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cookie-validate (npm)

MAL-2025-191569

Immediate action

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

npm uninstall cookie-validate

What this malware does

The package cookie-validate was found to contain malicious code.

Malicious versions

1 flagged

2.2.4

Indicators of compromise (SHA-256)

cfeb23f65da893a4cec4b2fbced2c1a73cbe6b08e1f2d5c5b35c4dae143318c1

759ee3039b2e22e1b76401c70ec7d3a1954d903ec6aa70da0a3721d65c1d3937

afc299602a1c16e6792db1c9961f8c7823d863b219ab2ede9bf112aac79c09e8

a2022a8cac8b6a1e26b8155b90c2a95c21daf20fbbce4cc10d49f836223c3a3f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cookie-validate (version 2.2.4).
If you installed it — respond
Remove cookie-validate from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If cookie-validate 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-validate on npm has been identified as a malicious package (version 2.2.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05708RLUA-2025-06102RLUA-2026-01224

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks cookie-validate-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