Which versions of ddxq_cms_tools are malicious?

The following npm versions of ddxq_cms_tools are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate ddxq_cms_tools if I installed it?

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

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

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

Search your lockfiles and build artifacts for ddxq_cms_tools (version 999.0.0).

Malicious package

ddxq_cms_toolsnpm

Advisory published Dec 23, 2025Updated Dec 24, 2025

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

Malicious code in ddxq_cms_tools (npm)

MAL-2025-192733

Immediate action

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

npm uninstall ddxq_cms_tools

What this malware does

The package ddxq_cms_tools was found to contain malicious code.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

5c6eb1a30aa7ad9099749819f42bb792d29c809ea58ff0d32514e1a3a4ce19fa

1c79b5bf164abe664b45e8c5ffcc1a0b7b68214b8b37182338b4c34ca4ae4b3a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06111

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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