Which versions of telegram-bot_api are malicious?

The following RubyGems versions of telegram-bot_api are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate telegram-bot_api if I installed it?

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

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

Yes — telegram-bot_api is associated with the RLMA-2024-05838, RLUA-2024-10359, RLUA-2026-09535 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 telegram-bot_api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for telegram-bot_api (version 0.1.0).

Malicious package

telegram-bot_apiRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

telegram-bot_api is a confirmed malicious RubyGems package (MAL-2024-7033) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in telegram-bot_api (RubyGems)

MAL-2024-7033

Immediate action

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

gem uninstall telegram-bot_api

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

0d4406591371452e65e2fe6bb85ba8fb613458a75ef1ff6df796f7400912ae3c

cb8c6b81681370fcfd5f37e9dacdcf7cc14d1249379d503d6d037a8259a2745a

02dab1e9f88e7a1293692564a5ae70c288abe558a5547eaf6aecd8c501726b01

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for telegram-bot_api (version 0.1.0).
If you installed it — respond
Remove telegram-bot_api 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 telegram-bot_api 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. telegram-bot_api on RubyGems has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05838RLUA-2024-10359RLUA-2026-09535

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks telegram-bot_api-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

Explore

All malware advisories How O3 detects malware Vulnerability database