Which versions of rbi-central are malicious?

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

How do I remediate rbi-central if I installed it?

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

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

Yes — rbi-central is associated with the RLMA-2024-05815, RLUA-2024-10336, RLUA-2026-09029 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 rbi-central across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rbi-central (version 0.0.2).

Malicious package

rbi-centralRubyGems

rbi-central is a confirmed malicious RubyGems package (MAL-2024-7010) 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 rbi-central (RubyGems)

MAL-2024-7010

Immediate action

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

gem uninstall rbi-central

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

a196317e1ba97aaf27dfc8a03ef37b6d7093f8e8cfd88306e5bb712dc9a37f74

26f347c457975cef3a0435fce0123edb7ece1a597d52a172b1fc5f60bfd69bbb

9f5bc68d313faabc456d4efad7660da86eddda135912c42373f315c4368cb204

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for rbi-central (version 0.0.2).
If you installed it — respond
Remove rbi-central 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 rbi-central 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. rbi-central 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-05815RLUA-2024-10336RLUA-2026-09029

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks rbi-central-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