Which versions of stnsxmp are malicious?

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

How do I remediate stnsxmp if I installed it?

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

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

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

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

Malicious package

stnsxmpnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

stnsxmp is a confirmed malicious npm package (MAL-2026-1857) that executes malicious code on install (malicious versions 0.0.1, 0.30.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stnsxmp (npm)

MAL-2026-1857

Immediate action

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

npm uninstall stnsxmp

What this malware does

The package stnsxmp was found to contain malicious code.

Malicious versions

2 flagged

0.0.10.30.1

Indicators of compromise (SHA-256)

ae3ea08bd0db07c366055b6edb3ab7ea69823fd665c2443527fbb6f44af8e9ec

6f71046374980b35d68230cf391bf580cd1ce68017bf6ac6373b72b01b9d9b67

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01592

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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