Which versions of supxmlparser are malicious?

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

How do I remediate supxmlparser if I installed it?

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

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

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

Search your lockfiles and build artifacts for supxmlparser (2 malicious versions).

Malicious package

supxmlparsernpm

Advisory published Nov 9, 2025Updated Dec 24, 2025

supxmlparser is a confirmed malicious npm package (MAL-2025-49446) that executes malicious code on install (malicious versions 0.30.1, 0.30.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in supxmlparser (npm)

MAL-2025-49446

Immediate action

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

npm uninstall supxmlparser

What this malware does

The package supxmlparser was found to contain malicious code.

Malicious versions

2 flagged

0.30.10.30.2

Indicators of compromise (SHA-256)

f3875bc6e2e97cfd10a8d926b80d7a78ac31781bad91e61e5960eadd34d87f56

a41bb309f7d0668ec6021e8ae4f127b32ce118c8332bbefb08de2546924819ec

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06506

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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