Which versions of libxmlussr1 are malicious?

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

How do I remediate libxmlussr1 if I installed it?

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

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

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

Malicious package

libxmlussr1npm

Advisory published Dec 9, 2025Updated Dec 10, 2025

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

MAL-2025-192427

Immediate action

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

npm uninstall libxmlussr1

What this malware does

The package libxmlussr1 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'libxmlussr1' @ 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)

08f90af0e1186fb0b75f135e5764cce07fe11f3d68115fe4195d556e7b0171da

53a26137f4b62749b9f491cb82c0c0f9d95f0fa03f7dcd2e8067b39b5de0e005

Detection & response playbook

Malicious package

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