Which versions of sturdyfetch21 are malicious?

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

How do I remediate sturdyfetch21 if I installed it?

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

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

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

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

Malicious package

sturdyfetch21npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

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

MAL-2025-192870

Immediate action

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

npm uninstall sturdyfetch21

What this malware does

The package sturdyfetch21 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

6def62a1c73266bbf0a75197528c456c51d75ce51043c36d7622713abdae8285

9ba69196889e05381da2622501c31fa4d044353988973b496b124beccb6f8466

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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