Which versions of sturdyfetch22 are malicious?

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

How do I remediate sturdyfetch22 if I installed it?

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

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

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

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

Malicious package

sturdyfetch22npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

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

MAL-2025-192871

Immediate action

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

npm uninstall sturdyfetch22

What this malware does

The package sturdyfetch22 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

ae7341999303a63adcfd5923f09a8a2b65c6cb4bec516036dd64e3cacbdf3a71

66259ae9063ad61d19e083ba9f5ef1526c033d803a16d457f3445a9487ab40dd

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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