Which versions of ddos-turbo-ecma are malicious?

The following npm versions of ddos-turbo-ecma are flagged malicious: 1.0.0. Treat any of these as compromised.

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

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

If ddos-turbo-ecma 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-ecma part of a known attack campaign?

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

Search your lockfiles and build artifacts for ddos-turbo-ecma (version 1.0.0).

Malicious package

ddos-turbo-ecmanpm

Advisory published Dec 23, 2025Updated Dec 24, 2025

ddos-turbo-ecma is a confirmed malicious npm package (MAL-2025-192731) 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 ddos-turbo-ecma (npm)

MAL-2025-192731

Immediate action

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

npm uninstall ddos-turbo-ecma

What this malware does

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bc0dfdc70e3b2fc09fdfc0605d6d2608cd1cc02af13e3d4c76a1b0c76ea3180b

3e64d8018dea45c4a342b7a09a99624a70f6db77000f42f534bc8df62b09c72f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ddos-turbo-ecma (version 1.0.0).
If you installed it — respond
Remove ddos-turbo-ecma 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-ecma 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-ecma 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

RLMA-2025-06109

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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