Which versions of libxmljs2-malicious are malicious?

The following npm versions of libxmljs2-malicious are flagged malicious: 0.19.9. Treat any of these as compromised.

How do I remediate libxmljs2-malicious if I installed it?

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

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

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

Search your lockfiles and build artifacts for libxmljs2-malicious (version 0.19.9).

Malicious package

libxmljs2-maliciousnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

libxmljs2-malicious is a confirmed malicious npm package (MAL-2026-1775) that executes malicious code on install (malicious version 0.19.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libxmljs2-malicious (npm)

MAL-2026-1775

Immediate action

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

npm uninstall libxmljs2-malicious

What this malware does

The package libxmljs2-malicious was found to contain malicious code.

Malicious versions

1 flagged

0.19.9

Indicators of compromise (SHA-256)

87b34082739a2c515181d5f404ff3092a7f29a538702fdc69dc2a8d5ad002965

392c5138d36ba42a009c8a27d8f4c158141a814c9990c022b422f540945e71e5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01408

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks libxmljs2-malicious-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