Which versions of @ctrl/deluge are malicious?

The following npm versions of @ctrl/deluge are flagged malicious: 7.2.1, 7.2.2. Treat any of these as compromised.

How do I remediate @ctrl/deluge if I installed it?

@ctrl/deluge 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 @ctrl/deluge — how do I know if it already compromised me?

If @ctrl/deluge 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 @ctrl/deluge part of a known attack campaign?

Yes — @ctrl/deluge is associated with the GHSA-wv45-cmjw-6456 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 @ctrl/deluge 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 @ctrl/deluge (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ctrl/deluge across your stack and pipelines.

Part of a larger attack: @ctrl published 14 malicious packages. See the full campaign →

Malicious package

@ctrl/delugenpm

@ctrl/deluge is a confirmed malicious npm package (MAL-2025-47131) that steals credentials and exfiltrates sensitive data (malicious versions 7.2.1, 7.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ctrl/deluge (npm)

MAL-2025-47131

Immediate action

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

npm uninstall @ctrl/deluge

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.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

2 flagged

7.2.17.2.2

Indicators of compromise (SHA-256)

d92c8c0ce4fcd72693ec79d2f5d112099c3e5d23e214a06327498cfa5b655fc4

2536c179ae1af5bc400a5aab117a1fc3565b387cea8bb01ce5c4355f92265199

ead1183b72db4d173cbfec370be6f38fd129dd895fdd3c05d6df16d7df6d17b9

ce81efcb1625c7bfeb4fd050f2361b24fea07902b538aed7d287e151c6f4257e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ctrl/deluge (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ctrl/deluge across your stack and pipelines.
If you installed it — respond
@ctrl/deluge 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 @ctrl/deluge 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 @ctrl/deluge 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. @ctrl/deluge on npm has been identified as a malicious package (versions 7.2.1, 7.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wv45-cmjw-6456

References

Detect & block this

O3 blocks @ctrl/deluge-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