Which versions of codon are malicious?

The following RubyGems versions of codon are flagged malicious: 22.55.2. Treat any of these as compromised.

How do I remediate codon if I installed it?

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

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

Yes — codon is associated with the RLMA-2024-05643, RLUA-2024-10162, RLUA-2026-07938 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 codon across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for codon (version 22.55.2).

Malicious package

codonRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in codon (RubyGems)

MAL-2024-6837

Immediate action

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

gem uninstall codon

Malicious versions

1 flagged

22.55.2

Indicators of compromise (SHA-256)

1c31d4c45fbf562133f109737c6521213f0099be22d679fdb41e9fffcf988608

ec1e55f24de7414cdd09c011ccbd7b0063a68975e4e43c866ce0eba1da6b3c55

9a324d6e3a9b3ae6d4cc9b230f803816ad73e0a57cd7dd2ed4ba103c39ad39eb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05643RLUA-2024-10162RLUA-2026-07938

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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