Which versions of libxmljs2superbank are malicious?

The following npm versions of libxmljs2superbank are flagged malicious: 0.30.2, 0.30.4, 0.31.0, 0.31.1, 999.0.0. Treat any of these as compromised.

How do I remediate libxmljs2superbank if I installed it?

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

If libxmljs2superbank 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.

Is libxmljs2superbank part of a known attack campaign?

Yes — libxmljs2superbank is associated with the RLMA-2025-06397 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find libxmljs2superbank across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for libxmljs2superbank (5 malicious versions).

Malicious package

libxmljs2superbanknpm

Advisory published Nov 9, 2025Updated Dec 24, 2025

libxmljs2superbank is a confirmed malicious npm package (MAL-2025-49419) that executes malicious code on install (malicious versions 0.30.2, 0.30.4, 0.31.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libxmljs2superbank (npm)

MAL-2025-49419

Immediate action

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

npm uninstall libxmljs2superbank

What this malware does

The package libxmljs2superbank was found to contain malicious code.

Malicious versions

5 flagged

0.30.20.30.40.31.00.31.1999.0.0

Indicators of compromise (SHA-256)

d241c65cb2ee896485fe87e83b157c504297c07f15718f59e7eeecbadf4a977d

7641393c334a2c740e595ed1f50e3b02b3d7c94dcac3a18974306f7c3f2b4d6c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06397

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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