Which versions of pytjon are malicious?

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

How do I remediate pytjon if I installed it?

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

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

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

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

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

Malicious package

pytjonPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10137

Immediate action

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

pip uninstall pytjon

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)

0004591d3437696c52a857657d39f1154571bceefdcb1c3bc315e6fcde432404

257bcd507f2e02bd591d2762722d5d449f4e740621b502ec8656af33bec5343e

f316841ab58a6ce44ae03c814c1fa5eb634bd720f7b3b526f229859b7d2bab5f

3365f2d8a9ad021dd065c1420d34a21f08f3b7f2be14d7f71760d6f13e8a6922

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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