Which versions of hrab0 are malicious?

The following RubyGems versions of hrab0 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate hrab0 if I installed it?

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

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

Yes — hrab0 is associated with the RLMA-2026-02408, RLUA-2026-08209 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 hrab0 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hrab0 (version 0.0.1).

Malicious package

hrab0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in hrab0 (RubyGems)

MAL-2026-7757

Immediate action

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

gem uninstall hrab0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a26f924966ff2091120a25ecc2a748e72066e0ef9d6770a2595b5ad463a426f5

4ab9d3f07200242c05cac84b9f42dfde8a11374e194765366eb8abbbee750520

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02408RLUA-2026-08209

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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