Which versions of telepycore are malicious?

The following PyPI versions of telepycore are flagged malicious: 1.0.1, 1.5.2, 1.5.3, 2.0.1, 2.0.2, 2.0.4, 2.0.5, 2.0.6, 2.0.7. Treat any of these as compromised.

How do I remediate telepycore if I installed it?

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

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

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

Malicious package

telepycorePyPI

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

MAL-2025-191889

Immediate action

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

pip uninstall telepycore

What this malware does

Package can only be used (requires additional triggering) to install a remote executable, ensure it starts on logon and name mimic network service. Though different versions contain different executables, they are mostly identified as malicious by multiple AVs and sandboxes, highlighting adding Defender exclusions and downloading further executables.

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

Campaign: 2025-04-telepycore

Reasons (based on the campaign):

peristence-autorun
Downloads and executes a remote executable.

Malicious versions

9 flagged

1.0.11.5.21.5.32.0.12.0.22.0.42.0.52.0.62.0.7

Indicators of compromise (SHA-256)

2dc747e122c81692ac6a483fcb68353bed82cd5894aa04ac1400f25e7b47fd86

c3dcd0a2a8162a703ef9d7b90566e4c55116a7f4f4d3b8759ca0d2640acd4ee4

a09e692d56a71711c2bdbd085d99e385d5fee6cc3478696248015800227889ac

b3ca7200cc390d10829cdc04d93b6d1a4be061d3abf73c5739030f1c1492d1f0

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for telepycore (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging telepycore across your stack and pipelines.
If you installed it — respond
telepycore 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 telepycore 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 telepycore 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. telepycore on PyPI has been identified as a malicious package (versions 1.0.1, 1.5.2, 1.5.3, 2.0.1, 2.0.2, 2.0.4, 2.0.5, 2.0.6, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-04-telepycore

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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