Which versions of xmenddddl are malicious?

The following npm versions of xmenddddl are flagged malicious: 999.999.999. Treat any of these as compromised.

How do I remediate xmenddddl if I installed it?

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

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

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

Search your lockfiles and build artifacts for xmenddddl (version 999.999.999).

Malicious package

xmenddddlnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

xmenddddl is a confirmed malicious npm package (MAL-2025-191603) that executes malicious code on install (malicious version 999.999.999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xmenddddl (npm)

MAL-2025-191603

Immediate action

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

npm uninstall xmenddddl

Malicious versions

1 flagged

999.999.999

Indicators of compromise (SHA-256)

a764327402e35f0a961a3981050e0cfd4281dfe3a4f62053737c2ce890bf5c98

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for xmenddddl (version 999.999.999).
If you installed it — respond
Remove xmenddddl 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 xmenddddl 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. xmenddddl on npm has been identified as a malicious package (version 999.999.999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06004

Credits

ReversingLabs · finder

Detect & block this

O3 blocks xmenddddl-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