Which versions of telegram-meetup_bot are malicious?

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

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

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

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

Yes — telegram-meetup_bot is associated with the RLMA-2024-05841, RLUA-2024-10362, RLUA-2026-09538 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-meetup_bot across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for telegram-meetup_bot (version 0.3.0).

Malicious package

telegram-meetup_botRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in telegram-meetup_bot (RubyGems)

MAL-2024-7036

Immediate action

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

gem uninstall telegram-meetup_bot

Malicious versions

1 flagged

0.3.0

Indicators of compromise (SHA-256)

756a2cd9ba277693e728db77a2629a63b37056fd79c0282f68deaab34504ea88

562cd46c8e20f57e00ee80b0d8c5bb1ac1f4ffca984f555b74e577a7809d227a

6e3ab42014720c3959a1cdc90322bf989c89f6eadbf87e72d05be34129c3d623

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05841RLUA-2024-10362RLUA-2026-09538

References

Credits

ReversingLabs · finder

Detect & block this

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