Which versions of heroku-tl are malicious?

The following PyPI versions of heroku-tl are flagged malicious: 2.1.0, 2.1.1, 2.2.2, 2.5.0, 2.5.1, 2.6.0, 2.8.0, 2.9.0, 3.0.0, 3.0.1, 3.1.0, 3.2.0, 3.2.1, 3.2.2, 3.2.5. Treat any of these as compromised.

How do I remediate heroku-tl if I installed it?

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

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

Yes — heroku-tl is associated with the RLMA-2025-01965, 2025-03-heroku-tl, RLUA-2026-00387, RLUA-2026-02070 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 heroku-tl 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 heroku-tl (15 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging heroku-tl across your stack and pipelines.

Malicious package

heroku-tlPyPI

Malicious code in heroku-tl (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2967

Immediate action

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

pip uninstall heroku-tl

What this malware does

Clone of a legit Telegram client, with a hidden code that, under some conditions, can attempt to destroy the Linux OS.

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

Campaign: 2025-03-heroku-tl

Reasons (based on the campaign):

clones-real-package
action-hidden-in-lib-usage

Malicious versions

15 flagged

2.1.02.1.12.2.22.5.02.5.12.6.02.8.02.9.03.0.03.0.13.1.03.2.03.2.13.2.23.2.5

Indicators of compromise (SHA-256)

0a8f4fc0a5d0503ac09d15275006031ce30676e8778cddddd61d8fd257fd3518

f65785e45b1a1412bb45fd3f8bbc75a9ba4709d4749e07b8db315d28c58cc1f7

8a78aff2389300306864bb3d44e1ac70675e128845a4d734dae5ffbc39076b93

f582fa05d5a878f06b3d751c56ce9c8231144aa385b567532baf91452d6af91c

e0f9dcd6289d0a3933488f9c5affeaaebd78d6ad3eb20d542b1e2782c068ca90

f0712a9afe745c4bc3354354515ea6ae3559f44a0084e181f890244801905dfd

cd936b22207b5a7a8164d664ed3f3bd13f58d8f3a53493a2e767f36221d1632b

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 heroku-tl (15 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging heroku-tl across your stack and pipelines.
If you installed it — respond
heroku-tl 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 heroku-tl 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 heroku-tl 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. heroku-tl on PyPI has been identified as a malicious package (versions 2.1.0, 2.1.1, 2.2.2, 2.5.0, 2.5.1, 2.6.0, 2.8.0, 2.9.0, and 7 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-019652025-03-heroku-tlRLUA-2026-00387RLUA-2026-02070

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks heroku-tl-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