Which versions of libxmljs9 are malicious?

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

How do I remediate libxmljs9 if I installed it?

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

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

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

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

Malicious package

libxmljs9npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

MAL-2026-1786

Immediate action

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

npm uninstall libxmljs9

What this malware does

The package libxmljs9 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

88b99961c4d89acc609ed4e68a7a05c61a2dd16b8d4be6622e1b605da29048a2

bf963cb34c40586e2ba2844d3ed3d480c0e296e6faf1c9530d62776ed081d59f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for libxmljs9 (version 0.30.1).
If you installed it — respond
Remove libxmljs9 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 libxmljs9 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. libxmljs9 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-01419

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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