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

redis-cookie-servernpm

redis-cookie-server is a confirmed malicious npm package (MAL-2026-15602) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in redis-cookie-server (npm)

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

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

f7bfa26302d0f6ed7b8514afde44ac4bd0a92fe4f6aee6e405ea435408215a13
01c94026a508b2ada8c891551c8ccd622f86c2ba2e7b6a7c181fc3eb538e2f1f

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 redis-cookie-server (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging redis-cookie-server across your stack and pipelines.

  2. If you installed it — respond

    Remove redis-cookie-server 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 redis-cookie-server 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 redis-cookie-server 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. redis-cookie-server on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jgx3-v64x-v2w5IN-MAL-2026-019245

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

redis-cookie-server (npm) malicious package — MAL-2026-15602 | O3 Security