Which versions of pythun are malicious?

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

How do I remediate pythun if I installed it?

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

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

Yes — pythun is associated with the RLMA-2024-09069, funcaptcha-ru 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 pythun across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pythun (version 1.0.0).

Part of a larger attack: funcaptcha-ru published 161 malicious packages. See the full campaign →

Malicious package

pythunPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

pythun is a confirmed malicious PyPI package (MAL-2024-10134) 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 pythun (PyPI)

MAL-2024-10134

Immediate action

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

pip uninstall pythun

What this malware does

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

Campaign: funcaptcha-ru

Reasons (based on the campaign):

infostealer

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

794fa71e6e5f976a6cc1fd246bd4641257c8c35ad8a1109287dd67fbf657dae6

7450f279deaf79ec6b1f7da761311923b60219eb9f13ec3da5ddef053b0755a2

821e1f5c73d728554e79f05bb2166bc33224be147539685e239f9244c792c2dd

ad1edd772f8f718ef5fcb9b3268798c13d691caa863c2518539ebf2746c19e44

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pythun (version 1.0.0).
If you installed it — respond
pythun 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 pythun 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. pythun 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

RLMA-2024-09069funcaptcha-ru

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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