Which versions of telcoo are malicious?

The following PyPI versions of telcoo are flagged malicious: 1.0.2, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate telcoo if I installed it?

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

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

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

Malicious package

telcooPyPI

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

MAL-2025-192386

Immediate action

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

pip uninstall telcoo

What this malware does

Running the module starts a reverse shell

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

Campaign: 2025-12-evil-rce

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.

Malicious versions

3 flagged

1.0.21.0.31.0.4

Indicators of compromise (SHA-256)

c96937a82adce2ecc6628245fd858587131511b4145c04f577ec25d8fa846577

e3f30e917ee86ce1c003daa06d10c8bc887a63c3661a06329cb3a3fa504494f5

4511475153946aa974031c1d3e939d6c92c9d911bbabbd4c2d9cb79059bdac1d

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 telcoo (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging telcoo across your stack and pipelines.
If you installed it — respond
telcoo 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 telcoo 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 telcoo 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. telcoo on PyPI has been identified as a malicious package (versions 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-12-evil-rce

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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