Which versions of telegram_bot-ruby are malicious?

The following RubyGems versions of telegram_bot-ruby are flagged malicious: 0.12.0. Treat any of these as compromised.

How do I remediate telegram_bot-ruby if I installed it?

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

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

Yes — telegram_bot-ruby is associated with the RLMA-2024-05843, RLUA-2024-10364, RLUA-2026-09540 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-ruby across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for telegram_bot-ruby (version 0.12.0).

Malicious package

telegram_bot-rubyRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

telegram_bot-ruby is a confirmed malicious RubyGems package (MAL-2024-7038) that executes malicious code on install (malicious version 0.12.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in telegram_bot-ruby (RubyGems)

MAL-2024-7038

Immediate action

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

gem uninstall telegram_bot-ruby

Malicious versions

1 flagged

0.12.0

Indicators of compromise (SHA-256)

d9c9c0b8df88fb0f569cbc5a7fb0c6130dd648f11d7d8bbb8f88e9f62688b3ad

319afbdc95389b7d55ad415ae74b502f95ca0752220109bcb11faec3f21ff295

9e149c7cc637828c416f03532f8f12ab6db44bede96b09c03692f6b9518df2f4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05843RLUA-2024-10364RLUA-2026-09540

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks telegram_bot-ruby-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