Which versions of libxmlrussia are malicious?

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

How do I remediate libxmlrussia if I installed it?

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

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

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

Malicious package

libxmlrussianpm

Advisory published Dec 9, 2025Updated Dec 10, 2025

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

MAL-2025-192395

Immediate action

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

npm uninstall libxmlrussia

What this malware does

The package libxmlrussia was found to contain malicious code.

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

c40f1e55e4a926ae8d822a3c0dc9f8a5b2f245e241da266a23811ecddb2162d7

09a896cf7e2a9565c72e2dbea89306401102334fe016a8819be5ab476cff9d8e

Detection & response playbook

Malicious package

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