Which versions of cookie-mapper are malicious?

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

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

Remove cookie-mapper 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-mapper — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for cookie-mapper (version 1.1.0).

Malicious package

cookie-mappernpm

Advisory published Dec 23, 2025Updated Mar 19, 2026

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

Malicious code in cookie-mapper (npm)

MAL-2025-192728

Immediate action

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

npm uninstall cookie-mapper

What this malware does

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

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

ca84ac95f6b058a02bdda6818d4f3e1c9d34b76f3b13ebcf2dbcb7913b496ba9

efe3ae0666fc23cea770581c1bc3ca124e00a25f8c4a4794d120a971589ad6d3

3377f391d6b338d969bfe31003bbb41bcc0fe858746737ca30dfe60e81e63fbf

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cookie-mapper (version 1.1.0).
If you installed it — respond
Remove cookie-mapper 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-mapper 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-mapper on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06101RLUA-2026-01222

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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