Which versions of python-fork are malicious?

The following PyPI versions of python-fork are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate python-fork if I installed it?

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

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

Yes — python-fork is associated with the 2026-09-python-fork, IN-MAL-2026-020471 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 python-fork across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for python-fork (2 malicious versions).

Malicious package

python-forkPyPI

Advisory published Sep 12, 2026Updated Sep 23, 2026

python-fork is a confirmed malicious PyPI package (MAL-2026-16142) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in python-fork (PyPI)

MAL-2026-16142

Immediate action

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

pip uninstall python-fork

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Importing the module starts a fork bomb, what can lead to destabilizing the system.

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

Campaign: 2026-09-python-fork

Reasons (based on the campaign):

other

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

0bff88696e931354b786185cde4b21e28c27407203c5733ac31b52b7186c1e78

ccd1d960319085a4aee1c389c4b394bfddd03f3c2af57f4d09bce88f9ad4a66d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for python-fork (2 malicious versions).
If you installed it — respond
python-fork 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 python-fork 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. python-fork on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-python-forkIN-MAL-2026-020471

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks python-fork-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