Which versions of ctf2libxmljs2 are malicious?

The following npm versions of ctf2libxmljs2 are flagged malicious: 0.30.2. Treat any of these as compromised.

How do I remediate ctf2libxmljs2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for ctf2libxmljs2 (version 0.30.2).

Malicious package

ctf2libxmljs2npm

Advisory published Dec 1, 2025Updated Dec 2, 2025

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

Malicious code in ctf2libxmljs2 (npm)

MAL-2025-191571

Immediate action

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

npm uninstall ctf2libxmljs2

What this malware does

The package ctf2libxmljs2 was found to contain malicious code.

Malicious versions

1 flagged

0.30.2

Indicators of compromise (SHA-256)

d7b9e4fe10e07d12bf96ada0392b3d01a59a259dd554620116748f4803649aaf

de69afa73f1f4886ac05efb1fce080314b4a0bc5f0a122bb50e7bd03f945db9b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05712

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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