Which versions of rate-beer are malicious?

The following RubyGems versions of rate-beer are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate rate-beer if I installed it?

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

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

Yes — rate-beer is associated with the RLMA-2024-05814, RLUA-2024-10335, RLUA-2026-09028 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 rate-beer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rate-beer (version 0.0.2).

Malicious package

rate-beerRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in rate-beer (RubyGems)

MAL-2024-7009

Immediate action

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

gem uninstall rate-beer

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

bc5a8c72ae6055e519d81530bfe308a36d4e6f0102bdcf535a7de9ec1066e19e

88c7f47a3fa243659a118865c023baa577f6625e17643577ce3e432ad3ef021c

b9e92028f7294327208b2d99319d62f2e4ae4a5baedc02475a3f98a2b203cb61

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05814RLUA-2024-10335RLUA-2026-09028

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks rate-beer-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