Which versions of pytc123 are malicious?

The following PyPI versions of pytc123 are flagged malicious: 3.1.0. Treat any of these as compromised.

How do I remediate pytc123 if I installed it?

Remove pytc123 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed pytc123 — how do I know if it already compromised me?

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

Yes — pytc123 is associated with the RLMA-2025-00500, GENERIC-simple-tests, RLUA-2026-00649 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 pytc123 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 pytc123 (version 3.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pytc123 across your stack and pipelines.

Malicious package

pytc123PyPI

Malicious code in pytc123 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-959

Immediate action

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

pip uninstall pytc123

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

3.1.0

Indicators of compromise (SHA-256)

92b1f19fd3f423421c8ed225ad7d35b6112d2be68c4c2863354bbda02d17f2f8

492a498d5e00e0da41b1e496c7ae5199c68f2b8d15630e865dab583c6df3666f

29916930efd9b23d2db0a812c00e77dcb672c494ae1d721e2201c1006625bf43

55d207b25c5190930d1551e291a45379d4a850e9b79502679ac231d5d7d554ea

749e03220e4ff640e9f75ca351af5c823d7987333643c89059a15c95c6188812

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pytc123 (version 3.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pytc123 across your stack and pipelines.
If you installed it — respond
Remove pytc123 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If pytc123 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 pytc123 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. pytc123 on PyPI has been identified as a malicious package (version 3.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-00500GENERIC-simple-testsRLUA-2026-00649

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks pytc123-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring