Which versions of ruboty_telegram are malicious?

The following RubyGems versions of ruboty_telegram are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ruboty_telegram if I installed it?

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

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

Yes — ruboty_telegram is associated with the RLMA-2024-05822, RLUA-2024-10343, RLUA-2026-09086 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 ruboty_telegram across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ruboty_telegram (version 1.0.0).

Malicious package

ruboty_telegramRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in ruboty_telegram (RubyGems)

MAL-2024-7017

Immediate action

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

gem uninstall ruboty_telegram

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

75f26dc6b88710170fbd35beeed9def2841fdcfa35c98fdccc3f27eb2d71161b

96393cd553d1f7b5685b8b78eab8647dc4db9db48781304205bfce3289599bb0

ee9b3f8c5bece0d9c5790809fb752091d917cb9107b6775a9e0314e6fcb1ff56

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05822RLUA-2024-10343RLUA-2026-09086

References

Credits

ReversingLabs · finder

Detect & block this

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