Which versions of libxmljs2as are malicious?

The following npm versions of libxmljs2as are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate libxmljs2as if I installed it?

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

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

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

Search your lockfiles and build artifacts for libxmljs2as (version 1.0.0).

Malicious package

libxmljs2asnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in libxmljs2as (npm)

MAL-2026-1779

Immediate action

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

npm uninstall libxmljs2as

What this malware does

The package libxmljs2as was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2bc318c19a22d8c699bdbaa688992e253c8f0d4c445c3a92cb33df012c1bde93

de41fa76c6b222189c7c40b6cbe21b3c9b05c3223356e88362a0c6f621e84dd6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01412

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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