Which versions of libxmljsololo3 are malicious?

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

How do I remediate libxmljsololo3 if I installed it?

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

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

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

Malicious package

libxmljsololo3npm

Advisory published Dec 11, 2025Updated Dec 11, 2025

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

Malicious code in libxmljsololo3 (npm)

MAL-2025-192459

Immediate action

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

npm uninstall libxmljsololo3

What this malware does

The package libxmljsololo3 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)

f5d1f93ba15e7b1dea2fd731f26d04e13c7ff43da48e5ec7921dfd34cb94879a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for libxmljsololo3 (all published versions).
If you installed it — respond
Remove libxmljsololo3 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 libxmljsololo3 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. libxmljsololo3 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 libxmljsololo3-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