Which versions of hrab2 are malicious?

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

How do I remediate hrab2 if I installed it?

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

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

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

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

Malicious package

hrab2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7759

Immediate action

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

gem uninstall hrab2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fd07e37c401a260d59dd42dc59c0782a91c325725e45b60633f5ef192bf63671

60c4cd08f2b4b39e2ca689280c0f78bbbd22403a9a7de5333b6f39fc206ef474

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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