Which versions of hackhg1778554737 are malicious?

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

How do I remediate hackhg1778554737 if I installed it?

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

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

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

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

Malicious package

hackhg1778554737RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7731

Immediate action

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

gem uninstall hackhg1778554737

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

18ebe5ce122ff0db3abadfd21b31f92131b80d6ffe0d93cd1181506ff2bfa2de

6281cb40ccc592c5581349954078c486269c0d0e90a5b5d0331eddcd4d40a7c3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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