Which versions of ddos-turbo-max are malicious?

The following npm versions of ddos-turbo-max are flagged malicious: 1.0.0, 1.0.1, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9. Treat any of these as compromised.

How do I remediate ddos-turbo-max if I installed it?

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

If ddos-turbo-max 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.

Is ddos-turbo-max part of a known attack campaign?

Yes — ddos-turbo-max is associated with the RLMA-2025-06110 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 ddos-turbo-max across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ddos-turbo-max (9 malicious versions).

Malicious package

ddos-turbo-maxnpm

Advisory published Dec 23, 2025Updated Dec 24, 2025

ddos-turbo-max is a confirmed malicious npm package (MAL-2025-192732) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ddos-turbo-max (npm)

MAL-2025-192732

Immediate action

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

npm uninstall ddos-turbo-max

What this malware does

The package ddos-turbo-max was found to contain malicious code.

Malicious versions

9 flagged

1.0.01.0.11.0.31.0.41.0.51.0.61.0.71.0.81.0.9

Indicators of compromise (SHA-256)

7a1859f449ba65fd57ad58da505a00053538470e7e05ecb33747f710b8afa871

60af90f55c99cdd17b11c3fcbf6fb3b0fcf15b42e35b1b1ab95817d4981c7211

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ddos-turbo-max (9 malicious versions).
If you installed it — respond
Remove ddos-turbo-max 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 ddos-turbo-max 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. ddos-turbo-max on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06110

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ddos-turbo-max-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

Explore

All malware advisories How O3 detects malware Vulnerability database