Which versions of that-fetch are malicious?

Every published version of that-fetch on npm is considered malicious. Remove the package entirely.

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

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

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

Yes — that-fetch is associated with the GHSA-cwjc-3f32-g7cg 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 that-fetch across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for that-fetch (all published versions).

Malicious package

that-fetchnpm

Advisory published Nov 4, 2026Updated Nov 4, 2026

that-fetch is a confirmed malicious npm package (MAL-2026-18638) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in that-fetch (npm)

MAL-2026-18638

Immediate action

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

npm uninstall that-fetch

What this malware does

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

28d56828b44836f8b55e591ad433f8b082433589f3275c892174bac0ac562ac6

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for that-fetch (all published versions).
If you installed it — respond
Remove that-fetch 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 that-fetch 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. that-fetch on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cwjc-3f32-g7cg

References

github.com

Detect & block this

O3 blocks that-fetch-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