Which versions of ddok-escapes are malicious?

The following npm versions of ddok-escapes are flagged malicious: 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7. Treat any of these as compromised.

How do I remediate ddok-escapes if I installed it?

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

If ddok-escapes 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 ddok-escapes part of a known attack campaign?

Yes — ddok-escapes is associated with the RLMA-2025-04498, RLUA-2025-04985, RLUA-2025-05718 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 ddok-escapes across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ddok-escapes (6 malicious versions).

Malicious package

ddok-escapesnpm

Advisory published Aug 28, 2025Updated Dec 2, 2025

ddok-escapes is a confirmed malicious npm package (MAL-2025-41549) that executes malicious code on install (malicious versions 4.3.2, 4.3.3, 4.3.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ddok-escapes (npm)

MAL-2025-41549

Immediate action

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

npm uninstall ddok-escapes

Malicious versions

6 flagged

4.3.24.3.34.3.44.3.54.3.64.3.7

Indicators of compromise (SHA-256)

d806f67302a11d1053127d8c0c0a671264235880bdd8c660d850f4822d5451e4

09a058c870df140549ed4ccff2a95bc57c703eaf36b3548534e614c40ce53027

25f502e5a0a977a490a0215143d626e2ec8b6c604fa50ba4f7cf6a4ae0d7b06d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ddok-escapes (6 malicious versions).
If you installed it — respond
Remove ddok-escapes 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 ddok-escapes 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. ddok-escapes on npm has been identified as a malicious package (versions 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04498RLUA-2025-04985RLUA-2025-05718

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ddok-escapes-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