Which versions of libxmljsololos are malicious?

Every published version of libxmljsololos on npm is considered malicious. Remove the package entirely.

How do I remediate libxmljsololos if I installed it?

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

If libxmljsololos 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 libxmljsololos across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for libxmljsololos (all published versions).

Malicious package

libxmljsololosnpm

Advisory published Dec 11, 2025Updated Dec 11, 2025

libxmljsololos is a confirmed malicious npm package (MAL-2025-192461) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libxmljsololos (npm)

MAL-2025-192461

Immediate action

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

npm uninstall libxmljsololos

What this malware does

The package libxmljsololos was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

25e710261901e3db0a1f8ea9a5b78dcab045a74cf66b298c408d203c68b2c500

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder

Detect & block this

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