Which versions of @deliveroo/reevent are malicious?

The following npm versions of @deliveroo/reevent are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate @deliveroo/reevent if I installed it?

@deliveroo/reevent is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @deliveroo/reevent — how do I know if it already compromised me?

If @deliveroo/reevent 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.

How do I find @deliveroo/reevent across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @deliveroo/reevent (version 1.0.1).

Malicious package

@deliveroo/reeventnpm

Advisory published Aug 4, 2026Updated Aug 5, 2026

@deliveroo/reevent is a confirmed malicious npm package (MAL-2026-11563) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @deliveroo/reevent (npm)

MAL-2026-11563

Immediate action

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

npm uninstall @deliveroo/reevent

What this malware does

npm/@deliveroo/reevent is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 (the "Shai-Hulud: Here We Go Again" wave) — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed version(s) were trojanized and republished by the worm after it reached an npm publish token belonging to a maintainer in this namespace; the payload enumerates every package a stolen token controls and republishes each with the same hook, so many packages under this scope were poisoned in the same short window. Every poisoned release adds a preinstall hook ("preinstall": "node setup.mjs") that runs on a bare npm install, before any project code. setup.mjs downloads a standalone Bun runtime and runs a byte-identical, heavily obfuscated ~728 KB second-stage credential stealer (shipped as Math_Symbol.js / math_init.js). It harvests GitHub, npm, AWS, GCP, Azure, HashiCorp Vault and Kubernetes credentials plus generic secrets and private keys (TruffleHog-style sweep), reads CI/CD secrets and identifies build runners, then republishes further packages the stolen token can reach. Rather than a fixed command-and-control host, it exfiltrates stolen findings to attacker-created GitHub repositories (descriptions reading "Shai-Hulud: Here We Go Again") and over DNS. Treat any environment that installed an affected version (with install scripts enabled) as compromised: rotate and revoke all reachable credentials (npm and GitHub tokens, cloud keys, Vault/Kubernetes secrets, and CI org/repo secrets). Part of the August 2026 npm worm that poisoned 400+ packages across many organizations.

Malicious versions

1 flagged

1.0.1

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @deliveroo/reevent (version 1.0.1).
If you installed it — respond
@deliveroo/reevent is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @deliveroo/reevent 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. @deliveroo/reevent on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Socket Threat Research Team · finder
Aikido Security · finder
SafeDep · finder

Detect & block this

O3 blocks @deliveroo/reevent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database