Which versions of telerape are malicious?

The following PyPI versions of telerape are flagged malicious: 0.0.0.dev0, 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate telerape if I installed it?

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

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

Yes — telerape is associated with the 2026-07-telerape 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 telerape across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for telerape (3 malicious versions).

Malicious package

telerapePyPI

Advisory published Jul 31, 2026Updated Jul 31, 2026

telerape is a confirmed malicious PyPI package (MAL-2026-11424) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.0.dev0, 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in telerape (PyPI)

MAL-2026-11424

Immediate action

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

pip uninstall telerape

What this malware does

Package places a reverse shell in the PTH file. In analyzed versions, the target was on localhost.

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

Campaign: 2026-07-telerape

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
abuses-pth

Malicious versions

3 flagged

0.0.0.dev01.0.01.0.1

Indicators of compromise (SHA-256)

21e8fc4f3dd969ec103ff1cb8a5bdba0d465bffffabe2615bc38d8e00606cffa

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for telerape (3 malicious versions).
If you installed it — respond
telerape 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 telerape 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. telerape on PyPI has been identified as a malicious package (versions 0.0.0.dev0, 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-telerape

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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