Which versions of libxmljs8 are malicious?

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

How do I remediate libxmljs8 if I installed it?

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

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

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

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

Malicious package

libxmljs8npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

MAL-2026-1785

Immediate action

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

npm uninstall libxmljs8

What this malware does

The package libxmljs8 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

b94c79ecc716a51c21594db9b827bf7f9a613ba50767250f6fed9d2a4ba16b88

404e110268457c33fbe28e62b22c0233f5dbf4b3b9f1feec6ff2b457e0fa244f

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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