Which versions of gfff5 are malicious?

The following npm versions of gfff5 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate gfff5 if I installed it?

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

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

Yes — gfff5 is associated with the IN-MAL-2026-018416 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 gfff5 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 gfff5 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gfff5 across your stack and pipelines.

Malicious package

gfff5npm

gfff5 is a confirmed malicious npm package (MAL-2026-14296) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gfff5 (npm)

MAL-2026-14296

Immediate action

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

npm uninstall gfff5

What this malware does

gfff5 advertises itself as a 'System binary configuration tool' but its actual behavior is covert surveillance. When the CLI is invoked, index.js silently installs Python 3.12 on Windows (via winget, or by downloading the python.org installer to %TEMP% and running it with /quiet InstallAllUsers=0 PrependPath=1), then pip-installs the libraries required by a bundled pointer.py. pointer.py registers global low-level keyboard hooks via the keyboard module (including a raw mash_hook), captures screenshots with mss / ImageGrab, reads clipboard contents via pyperclip, walks other application windows' UI trees with uiautomation.WalkControl, and POSTs the collected text and images to the hardcoded author endpoint https://iq-sec.vercel.app/api. Stealth features (blank window titles, transparent overlay, a panic_exit hotkey, and source comments labeling the installer 'GHOST INSTALLER — No UI, No Admin Popup') confirm the behavior is intentionally hidden from the user and unrelated to the package's declared purpose.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2f12f82dc8c54282b428617c03537a54f3361841b02233b6626eae6f1e8ec4ee

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

Campaign

IN-MAL-2026-018416

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database