Which versions of libxmljs13 are malicious?

The following npm versions of libxmljs13 are flagged malicious: 0.30.1. Treat any of these as compromised.

How do I remediate libxmljs13 if I installed it?

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

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

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

Search your lockfiles and build artifacts for libxmljs13 (version 0.30.1).

Malicious package

libxmljs13npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in libxmljs13 (npm)

MAL-2026-1773

Immediate action

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

npm uninstall libxmljs13

What this malware does

The package libxmljs13 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

39c0f2e4742990ddec06fc178a7884b1e9ea2e084f39be9835f70a8d41233d1c

38dafad617301c1edf5722feddd7023a1e39feb06be970b19e713e38d0038ff7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01406

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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