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 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-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?

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

Malicious package

cookie-mappernpm

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cookie-mapper (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cookie-mapper across your stack and pipelines.
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 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-mapper 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-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