Which versions of superbankxmlparser are malicious?

The following npm versions of superbankxmlparser are flagged malicious: 0.30.2, 0.30.4, 0.31.2, 0.31.3. Treat any of these as compromised.

How do I remediate superbankxmlparser if I installed it?

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

If superbankxmlparser 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 superbankxmlparser part of a known attack campaign?

Yes — superbankxmlparser is associated with the RLMA-2025-06505 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 superbankxmlparser across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for superbankxmlparser (4 malicious versions).

Malicious package

superbankxmlparsernpm

Advisory published Nov 9, 2025Updated Dec 24, 2025

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

Malicious code in superbankxmlparser (npm)

MAL-2025-49441

Immediate action

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

npm uninstall superbankxmlparser

What this malware does

The package superbankxmlparser was found to contain malicious code.

Malicious versions

4 flagged

0.30.20.30.40.31.20.31.3

Indicators of compromise (SHA-256)

cac4441be445354aa3f3d44199629ebd0cb6c7c07a069a706bcf349ea0afd27e

228272c20978b84c7176b4ffdb539fe4ab1dfa8bd5671edce0cdcbe23dd379eb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06505

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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