Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

cookie-easenpm

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

MAL-2026-6812
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cookie-ease

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

10 flagged
1.0.01.0.51.0.61.0.71.0.81.0.91.1.11.1.21.1.31.1.5

Indicators of compromise (SHA-256)

e657448e95c84051d3c103da0e4bd744f5bc6cbbeedad66099d1ecf4681a65d5

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove cookie-ease 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.

  3. Did it already run?

    If cookie-ease 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.

  4. How O3 protects you

    O3 blocks cookie-ease 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-ease on npm has been identified as a malicious package (versions 1.0.0, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.1, 1.1.2, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-prqq-9q57-x2pq

References

Detect & block this

O3 blocks cookie-ease-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.