Which versions of hackgit1778554705 are malicious?

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

How do I remediate hackgit1778554705 if I installed it?

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

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

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

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

Malicious package

hackgit1778554705RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7730

Immediate action

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

gem uninstall hackgit1778554705

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f7adaf5729aa0ff7af470d39aaa60a2289671987a05f143f77e02c02040afa97

e83fb4bfd1ba5d2974380253b880332e34e4aff250a12e1fa5fc9334f686fc3e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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