Which versions of tenacious-fetch are malicious?

The following npm versions of tenacious-fetch are flagged malicious: 2.3.2, 2.3.3. Treat any of these as compromised.

How do I remediate tenacious-fetch if I installed it?

tenacious-fetch is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tenacious-fetch — how do I know if it already compromised me?

If tenacious-fetch was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is tenacious-fetch part of a known attack campaign?

Yes — tenacious-fetch is associated with the GHSA-vh97-57mq-739v 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 tenacious-fetch across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tenacious-fetch (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tenacious-fetch across your stack and pipelines.

Malicious package

tenacious-fetchnpm

Malicious code in tenacious-fetch (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191023

Immediate action

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

npm uninstall tenacious-fetch

What this malware does

The package tenacious-fetch was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

2.3.22.3.3

Indicators of compromise (SHA-256)

0c44fc9d1c7099876e590cd69eb0d5ff3928dcc439cfe74cce255584a3455cf9

61051d9fdf4393e5d5b5336a35ce010a5bd613ab5e8c9b1f45c9c3a409f365c5

711a664c841c44504bae9b7dd5e4ecf3379725fc1ece1785821a7990e4de9e64

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tenacious-fetch (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tenacious-fetch across your stack and pipelines.
If you installed it — respond
tenacious-fetch is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tenacious-fetch was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tenacious-fetch before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. tenacious-fetch on npm has been identified as a malicious package (versions 2.3.2, 2.3.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vh97-57mq-739v

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tenacious-fetch-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring