Which versions of sturdyfetch9 are malicious?

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

How do I remediate sturdyfetch9 if I installed it?

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

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

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

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

Malicious package

sturdyfetch9npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

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

MAL-2025-192875

Immediate action

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

npm uninstall sturdyfetch9

What this malware does

The package sturdyfetch9 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

be820b2548829337d71ab6d5a9d5a14c75e922e6e55126a634a46ebeff504d18

248e8cc5eaaf408613cdcd4d2ddf795f590a40d46491d4b0c57b910419280ecc

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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