Which versions of cookie-breaker are malicious?

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

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

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

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

Yes — cookie-breaker is associated with the RLMA-2025-06100, RLUA-2026-01221 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-breaker 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-breaker (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-breaker across your stack and pipelines.

Malicious package

cookie-breakernpm

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

MAL-2025-192727

Immediate action

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

npm uninstall cookie-breaker

What this malware does

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

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

0a13a13f5d53e7ca5aa83648bc2e29bff5f109099069a902e61eb975c3f0a017

b64a69ed1f4bd909ec9439986055d180490e4928aba8d08b45b4645956f63b14

4f6fdd5ed81eb56678538e9740eb8ecbb7422bf12b2f8267a35d8ef5fb0887ae

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-breaker (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-breaker across your stack and pipelines.
If you installed it — respond
Remove cookie-breaker 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-breaker 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-breaker 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-breaker 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-06100RLUA-2026-01221

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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