Which versions of libxmljs2qaz are malicious?

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

How do I remediate libxmljs2qaz if I installed it?

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

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

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

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

Malicious package

libxmljs2qaznpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

MAL-2026-1780

Immediate action

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

npm uninstall libxmljs2qaz

What this malware does

The package libxmljs2qaz was found to contain malicious code.

Malicious versions

1 flagged

0.30.2

Indicators of compromise (SHA-256)

534a955de690d55e564ad3c74e1a773f14e637388646c1fa1246b53a75356403

4f64f090b82381f264f574df9a6c965210764f25bcc6e57a1a0811cbca70fc20

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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