Which versions of fat-fingered are malicious?

The following npm versions of fat-fingered are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate fat-fingered if I installed it?

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

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

Yes — fat-fingered is associated with the GHSA-qwjf-7284-qjvw 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 fat-fingered 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 fat-fingered (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fat-fingered across your stack and pipelines.

Malicious package

fat-fingerednpm

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

MAL-2025-191090

Immediate action

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

npm uninstall fat-fingered

What this malware does

The package fat-fingered 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

1.0.11.0.2

Indicators of compromise (SHA-256)

77d5770972318f63a00eb2722c056f2e554e8970abd97f94cba9a3dde292a8d8

2203a40bba917587bc9bc8102dbcdabc248f061900f769a1eb94f86ef202e97e

9b5e127ac8099a8bee6fc42a5c3911a275384f00af4cd97082dde08a2bf2704f

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 fat-fingered (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fat-fingered across your stack and pipelines.
If you installed it — respond
fat-fingered 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 fat-fingered 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 fat-fingered 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. fat-fingered on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qwjf-7284-qjvw

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks fat-fingered-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