Which versions of sturdyfetch4 are malicious?

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

How do I remediate sturdyfetch4 if I installed it?

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

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

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

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

Malicious package

sturdyfetch4npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

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

MAL-2025-192873

Immediate action

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

npm uninstall sturdyfetch4

What this malware does

The package sturdyfetch4 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

079f37214390f0880f70f1f2bd2c7c34e350b0a74e69bbc0f679382bb0c8a12e

b0a1f215475fb968430542436e57b8aecaad84bcf2c31d52775c8ea1f0c8b3e7

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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