Which versions of stnsxmp3 are malicious?

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

How do I remediate stnsxmp3 if I installed it?

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

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

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

Search your lockfiles and build artifacts for stnsxmp3 (version 0.30.1).

Malicious package

stnsxmp3npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

stnsxmp3 is a confirmed malicious npm package (MAL-2026-1858) that executes malicious code on install (malicious version 0.30.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stnsxmp3 (npm)

MAL-2026-1858

Immediate action

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

npm uninstall stnsxmp3

What this malware does

The package stnsxmp3 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

5fe72f8d1f44f9fecf26723940a62a4983b73cd18aa7c56b3b978b9b4283405c

7ceb45e3044f3a3acbefdbdf144ca9aae81091d1cfdf84f5768de4df7176a231

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01593

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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