Which versions of telegram-bot_ruby are malicious?

The following RubyGems versions of telegram-bot_ruby are flagged malicious: 0.1.7. 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-05840, RLUA-2024-10361, RLUA-2026-09537 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.1.7).

Malicious package

telegram-bot_rubyRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in telegram-bot_ruby (RubyGems)

MAL-2024-7035

Immediate action

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

gem uninstall telegram-bot_ruby

Malicious versions

1 flagged

0.1.7

Indicators of compromise (SHA-256)

526d0eefbb4c600dd35b945c809dd1cf3413cb66cdfcdb6562df946be84f8a01

9fccc485e8c4837850ae3167171ba97b98a3db781d2fbd173713640b2aa9ea40

ca43f889a8a21bfc812247acba4fd1ba1fa4897b8cc553631d797c1d46c1ed2c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for telegram-bot_ruby (version 0.1.7).
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.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05840RLUA-2024-10361RLUA-2026-09537

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