Which versions of hraq1 are malicious?

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

How do I remediate hraq1 if I installed it?

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

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

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

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

Malicious package

hraq1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7763

Immediate action

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

gem uninstall hraq1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

be255b23f684a713f486d22b26eb04bf9a409cbb8c06bd447547e3284a28038b

c3ec66218e8cd9dd123c5d0dbcc8a1ce4de2c2bd9ad88ce3b4d8ee22707f5194

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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