Which versions of ggfmttygl are malicious?

The following PyPI versions of ggfmttygl are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ggfmttygl if I installed it?

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

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

Yes — ggfmttygl is associated with the 2026-05-ggfmttygl 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 ggfmttygl 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 ggfmttygl (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 ggfmttygl across your stack and pipelines.

Malicious package

ggfmttyglPyPI

Malicious code in ggfmttygl (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3405

Immediate action

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

pip uninstall ggfmttygl

What this malware does

Package is disguised as a utility, but in fact loads encrypted code as modules. However, loading it requires knowing the decryption key which is not included in the package.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-05-ggfmttygl

Reasons (based on the campaign):

obfuscation
The malicious code is intentionally included in a dependency of the package

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e741cc1df48cc526ad3a27ac702f5dea403723557b4a485f84847340310d66e5

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 ggfmttygl (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 ggfmttygl across your stack and pipelines.
If you installed it — respond
ggfmttygl 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 ggfmttygl 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 ggfmttygl 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. ggfmttygl on PyPI 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

2026-05-ggfmttygl

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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