Which versions of hraq0 are malicious?

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

How do I remediate hraq0 if I installed it?

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

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

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

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

Malicious package

hraq0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7762

Immediate action

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

gem uninstall hraq0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a3181f23ba85a108a04e23ac511d27e8cdffeda7f1c7ecbefce27d97248ae801

d04bcfd860812058411f04ac7ac0f8409fc841a085569f8e5ac0d72f1f5a0fd8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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