Which versions of hraq4 are malicious?

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

How do I remediate hraq4 if I installed it?

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

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

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

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

Malicious package

hraq4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7766

Immediate action

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

gem uninstall hraq4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

73812adc86ee96f30dfce128baa8b2855742932658682cb20b364fa3f69395bd

a93632934c910070f8a7b70f9e8e7e7cd3e7af45ff7c4d70d89c802c414cf764

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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