Which versions of rafka-rb are malicious?

The following RubyGems versions of rafka-rb are flagged malicious: 5000.1.0. Treat any of these as compromised.

How do I remediate rafka-rb if I installed it?

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

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

Yes — rafka-rb is associated with the RLMA-2026-00955, RLUA-2026-09025 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 rafka-rb across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rafka-rb (version 5000.1.0).

Malicious package

rafka-rbRubyGems

Advisory published Mar 18, 2026Updated Sep 24, 2026

rafka-rb is a confirmed malicious RubyGems package (MAL-2026-1919) that executes malicious code on install (malicious version 5000.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rafka-rb (RubyGems)

MAL-2026-1919

Immediate action

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

gem uninstall rafka-rb

Malicious versions

1 flagged

5000.1.0

Indicators of compromise (SHA-256)

262c6737f306096ecbe8a835597955d7555614fa6e9473a5f3d32a35bf218a26

6b20ef78f04ef9adc87e9d528d403910045bc071e885e4e669be7f1661229594

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-00955RLUA-2026-09025

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks rafka-rb-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