Which versions of libxmljs2v2 are malicious?

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

How do I remediate libxmljs2v2 if I installed it?

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

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

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

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

Malicious package

libxmljs2v2npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

libxmljs2v2 is a confirmed malicious npm package (MAL-2026-1781) 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 libxmljs2v2 (npm)

MAL-2026-1781

Immediate action

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

npm uninstall libxmljs2v2

What this malware does

The package libxmljs2v2 was found to contain malicious code.

Malicious versions

1 flagged

0.30.2

Indicators of compromise (SHA-256)

b381a1ea0eef3aacb56295643116f3543ae656d42290550c939db340c17ea9c2

a5fa602a5ab85b1160b292a89e2a2e96a612f35e672eef62da700fe7fe8a45d7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for libxmljs2v2 (version 0.30.2).
If you installed it — respond
Remove libxmljs2v2 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 libxmljs2v2 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. libxmljs2v2 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-2026-01414

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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