Which versions of pypdf-fork are malicious?

The following PyPI versions of pypdf-fork are flagged malicious: 6.10.2, 6.10.3. Treat any of these as compromised.

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

pypdf-fork establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed pypdf-fork — how do I know if it already compromised me?

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

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

Malicious package

pypdf-forkPyPI

Malicious code in pypdf-fork (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2999

Immediate action

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

pip uninstall pypdf-fork

What this malware does

During importing the module, package sends a beacon notification to the owner. The package has no other differences from the original legitimate "pypdf".

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2026-04-pypdf-fork

Reasons (based on the campaign):

clones-real-package

Malicious versions

2 flagged

6.10.26.10.3

Indicators of compromise (SHA-256)

c3a651b0cc8ca7cc4fcae91ff3160af205a97d0aacacd8e88d76c04ce013bd02

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pypdf-fork (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pypdf-fork across your stack and pipelines.
If you installed it — respond
pypdf-fork establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If pypdf-fork 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 pypdf-fork 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. pypdf-fork on PyPI has been identified as a malicious package (versions 6.10.2, 6.10.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-pypdf-fork

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pypdf-fork-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring