Which versions of libxmljs2varkek are malicious?

The following npm versions of libxmljs2varkek are flagged malicious: 0.30.3. Treat any of these as compromised.

How do I remediate libxmljs2varkek if I installed it?

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

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

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

Search your lockfiles and build artifacts for libxmljs2varkek (version 0.30.3).

Malicious package

libxmljs2varkeknpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in libxmljs2varkek (npm)

MAL-2026-1784

Immediate action

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

npm uninstall libxmljs2varkek

What this malware does

The package libxmljs2varkek was found to contain malicious code.

Malicious versions

1 flagged

0.30.3

Indicators of compromise (SHA-256)

dca2bba72e9cb49ebdfd12b0e0c13fdb3bc05c49177f2180d633d58209926d43

105532eb3eb77add838af434775d055cfa81507c242912a84540c4b3ee3f4c70

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01417

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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