Which versions of libxmljsololoq are malicious?

The following npm versions of libxmljsololoq are flagged malicious: 0.30.4. Treat any of these as compromised.

How do I remediate libxmljsololoq if I installed it?

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

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

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

Search your lockfiles and build artifacts for libxmljsololoq (version 0.30.4).

Malicious package

libxmljsololoqnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in libxmljsololoq (npm)

MAL-2026-1787

Immediate action

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

npm uninstall libxmljsololoq

What this malware does

The package libxmljsololoq was found to contain malicious code.

Malicious versions

1 flagged

0.30.4

Indicators of compromise (SHA-256)

60e8d696d16b3d5908711c35e7bc322e4fa79009c5bb125a1da8532ead82c8c5

b917faeab4059e14cdedb014a3275b35b1d40faf75e4e3930d78c92630e4a597

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01420

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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