Which versions of pythom are malicious?

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

How do I remediate pythom if I installed it?

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

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

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

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

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

Malicious package

pythomPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10131

Immediate action

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

pip uninstall pythom

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)

2e2366114ba5b938912aa865b90651bf2b2743aa56e5fd8a47d07089773538d5

463a280421753d31676f16f719a48d11bea28d193fe5f1ed8fbbf07836e0c716

7d368725a42952945fcd115620dbd4395ff77c147f47ca5f3a1658f62f9d44f2

bcb680823df39a324ba4d1e8e2fddd3af59001d3a1ca75684ed7d2162355fa7c

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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