Which versions of telegram-notifications are malicious?

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

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

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

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

Yes — telegram-notifications is associated with the RLMA-2024-05842, RLUA-2024-10363, RLUA-2026-09539 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-notifications across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for telegram-notifications (version 0.0.1).

Malicious package

telegram-notificationsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in telegram-notifications (RubyGems)

MAL-2024-7037

Immediate action

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

gem uninstall telegram-notifications

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

137d5eb381ec11495f69be5461a5affafaea2b05497702fdd1f4af51670797f6

78cd3dbc6c71754162686e8366435e86574764f59bb97f17a3517096885c2dae

8f213d5de849b20ba52cf63dd556da8d4cd0f76f135998e5fef6a6e2bb867088

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05842RLUA-2024-10363RLUA-2026-09539

References

Credits

ReversingLabs · finder

Detect & block this

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