Which versions of libxmlussr2 are malicious?

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

How do I remediate libxmlussr2 if I installed it?

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

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

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

Malicious package

libxmlussr2npm

Advisory published Dec 9, 2025Updated Dec 10, 2025

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

MAL-2025-192394

Immediate action

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

npm uninstall libxmlussr2

What this malware does

The package libxmlussr2 was found to contain malicious code.

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

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.30.2

Indicators of compromise (SHA-256)

771d953180e5f134a1baec570a2b913442d1541937204f2c3b222e3a056ba688

cef3040d3e54888147d11d2b7de509cbf77a77b93a7d5a6082cb7575d20a6d43

Detection & response playbook

Malicious package

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