Which versions of fonafx are malicious?

The following PyPI versions of fonafx are flagged malicious: 0.1, 0.2, 0.3. Treat any of these as compromised.

How do I remediate fonafx if I installed it?

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

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

Yes — fonafx is associated with the 2025-07-0x9xnx 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 fonafx 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 fonafx (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fonafx across your stack and pipelines.

Malicious package

fonafxPyPI

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

MAL-2025-191733

Immediate action

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

pip uninstall fonafx

What this malware does

Series of packages mostly with an obfuscated infostealer attempting to collect Chrome data. While discord webhook is usually set to an example, there are other, correct uploading URLs

Some of related packages only test partial malicious code, like webhooks from overwritten setup.py

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

Campaign: 2025-07-0x9xnx

Reasons (based on the campaign):

infostealer
obfuscation
exfiltration-browser-data
exfiltration-crypto
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.10.20.3

Indicators of compromise (SHA-256)

39fc9bb7b3be55340ba096fba0fe4def1d25f83244fbd3119a3d6529ece10c3c

9441463f029726ea263225e9b0092d82b049e2d7a4e059becd24f5e23c70a906

0267b4d7fd9ee0253410076f6b62cca6fa501e01a6379df392d74e2904d7eba6

a6d458ce9f3c48b182c596efb5ea0f5f923e14452d2faa5d273e0556fa8e9e05

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

Campaign

2025-07-0x9xnx

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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