Which versions of libxmljs2var are malicious?

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

How do I remediate libxmljs2var if I installed it?

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

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

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

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

Malicious package

libxmljs2varnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

MAL-2026-1782

Immediate action

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

npm uninstall libxmljs2var

What this malware does

The package libxmljs2var was found to contain malicious code.

Malicious versions

1 flagged

0.30.2

Indicators of compromise (SHA-256)

49f710421336d5662673e485b3bcf8b5fab6151f9f5a9fd056ecce702c76f068

5d5a63c57900c57550f9f05d096d53bdde29b77e1c643f62d1e5bd0329aeb6d8

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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