Which versions of sturdyfetch19 are malicious?

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

How do I remediate sturdyfetch19 if I installed it?

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

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

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

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

Malicious package

sturdyfetch19npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

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

MAL-2025-192869

Immediate action

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

npm uninstall sturdyfetch19

What this malware does

The package sturdyfetch19 was found to contain malicious code.

Malicious versions

1 flagged

0.30.1

Indicators of compromise (SHA-256)

791a9dc5a23e15d33878608a2be71f216e851c9a1cd046cfd7cf985d5dda73bd

99a862ff96c29fddb5563fbd26399572f9a11628f41a3c5c7dd82b345a557136

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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