Which versions of hrab3 are malicious?

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

How do I remediate hrab3 if I installed it?

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

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

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

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

Malicious package

hrab3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

hrab3 is a confirmed malicious RubyGems package (MAL-2026-7760) 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 hrab3 (RubyGems)

MAL-2026-7760

Immediate action

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

gem uninstall hrab3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

617ead8b78aa1c7204de12fba9651f47cf480ff63d34d6c5271fbdeec102cb00

fb1dcba033ff1d3ed926e932fafea0df0c8ec3701a6a174db55bafac7728b67e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hrab3 (version 0.0.1).
If you installed it — respond
Remove hrab3 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 hrab3 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. hrab3 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-02411RLUA-2026-08212

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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