Which versions of libxmljs2147 are malicious?

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

How do I remediate libxmljs2147 if I installed it?

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

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

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

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

Malicious package

libxmljs2147npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

MAL-2026-1776

Immediate action

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

npm uninstall libxmljs2147

What this malware does

The package libxmljs2147 was found to contain malicious code.

Malicious versions

1 flagged

0.30.2

Indicators of compromise (SHA-256)

aec889e53953af18ce5e2019c1bfd62c29fbb7778bc3f7ac2b0777d2817ea495

00cf0cb943f32607984ca5d580d5474570be4e15af662a7f4c4c61d3c1fc245d

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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