Which versions of jaconda-telegram are malicious?

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

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

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

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

Yes — jaconda-telegram is associated with the RLMA-2024-05754, RLUA-2024-10273, RLUA-2026-08236 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 jaconda-telegram across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jaconda-telegram (version 1.0).

Malicious package

jaconda-telegramRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in jaconda-telegram (RubyGems)

MAL-2024-6948

Immediate action

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

gem uninstall jaconda-telegram

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

82ffe0ab3f01aa905f77cc5052b8692bf60b45bd0fabc2970e20778625f3641c

87c061f8867ecefe76ab7bfdea1fdd84368be3e1e0f8ffd60235745c6a7391ca

59945587c881006a73bc58aba14a9b9cfb95e859498bb45ca6f4ce169a799734

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05754RLUA-2024-10273RLUA-2026-08236

References

Credits

ReversingLabs · finder

Detect & block this

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