Which versions of libxmljsololo2 are malicious?

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

How do I remediate libxmljsololo2 if I installed it?

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

If libxmljsololo2 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.

How do I find libxmljsololo2 across my projects, lockfiles, and CI pipelines?

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

Malicious package

libxmljsololo2npm

Advisory published Dec 9, 2025Updated Dec 10, 2025

libxmljsololo2 is a confirmed malicious npm package (MAL-2025-192426) 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 libxmljsololo2 (npm)

MAL-2025-192426

Immediate action

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

npm uninstall libxmljsololo2

What this malware does

The package libxmljsololo2 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'libxmljsololo2' @ 0.30.2 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

0.30.2

Indicators of compromise (SHA-256)

e4990f2ad9b80a96f05d335d0d8f89fbe25f5b84b3f3d4c1c9f02b1dea179710

ddf08b4bf0c122f751f82c3c5b909759570d84e47e5059bde5729221ae910a15

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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