Which versions of sturdyfetch15 are malicious?

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

How do I remediate sturdyfetch15 if I installed it?

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

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

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

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

Malicious package

sturdyfetch15npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

sturdyfetch15 is a confirmed malicious npm package (MAL-2025-192866) 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 sturdyfetch15 (npm)

MAL-2025-192866

Immediate action

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

npm uninstall sturdyfetch15

What this malware does

The package sturdyfetch15 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

abc50d5e24e7f1943131531e4e6a81c0ab63b07dbada4a54ac860e9f48ee096f

8efa01bf8ae7c64fda2970ecad836d73ed8625102c4a109ea1bff1e09c785057

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sturdyfetch15 (version 0.30.1).
If you installed it — respond
Remove sturdyfetch15 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 sturdyfetch15 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. sturdyfetch15 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-2025-06494

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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