Which versions of sturdyfetch5 are malicious?

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

How do I remediate sturdyfetch5 if I installed it?

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

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

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

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

Malicious package

sturdyfetch5npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

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

MAL-2025-192874

Immediate action

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

npm uninstall sturdyfetch5

What this malware does

The package sturdyfetch5 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

297f36efbf99593f12bf39022be65de9b56f005f9744ccdc77aea1528f095530

6a2d25bc6a8841e27c7ca62967ac6079c746e5dda54fd9e62fe798c395021ed4

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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