Which versions of first-gem_rakesh are malicious?

The following RubyGems versions of first-gem_rakesh are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate first-gem_rakesh if I installed it?

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

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

Yes — first-gem_rakesh is associated with the RLMA-2024-05701, RLUA-2024-10220, RLUA-2026-08083 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 first-gem_rakesh across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for first-gem_rakesh (version 0.1.0).

Malicious package

first-gem_rakeshRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in first-gem_rakesh (RubyGems)

MAL-2024-6895

Immediate action

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

gem uninstall first-gem_rakesh

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

c9995b25a563ac0b36c3d2f7a480c4578ed99daccbc09e73b20dccc8e0b4069d

d6d6ab50b93f15a2d1bdca1e43cff4f23dabaf72f0bdfec86fa3a73b70d34ed8

608b4ad6454508a587adffd6e2d184728a62f51809a8dcd4cd8d00304df2c7c9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05701RLUA-2024-10220RLUA-2026-08083

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks first-gem_rakesh-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