Which versions of fwf are malicious?

Every published version of fwf on npm is considered malicious. Remove the package entirely.

How do I remediate fwf if I installed it?

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

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

Yes — fwf is associated with the GHSA-5rjh-56g3-j7x2 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 fwf across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fwf (all published versions).

Malicious package

fwfnpm

Advisory published Jul 30, 2026Updated Jul 31, 2026

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

Malicious code in fwf (npm)

MAL-2026-11314

Immediate action

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

npm uninstall fwf

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)

67afa7fe22e11e200dbb0a033b897eb7ff275ba6b5c33ec15e1371bf1b8feb08

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for fwf (all published versions).
If you installed it — respond
Remove fwf 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 fwf 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. fwf 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-5rjh-56g3-j7x2

References

github.com

Detect & block this

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