Which versions of hacksvn1778554764 are malicious?

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

How do I remediate hacksvn1778554764 if I installed it?

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

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

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

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

Malicious package

hacksvn1778554764RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7732

Immediate action

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

gem uninstall hacksvn1778554764

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2ee7f05774c09a97efb093dc46013bb6437f4f4725ce35138863e4102dc13e7e

c6bc0aaedc65fcb04bc4391d343f65e78618788e3279831d18c1fda9b6de6215

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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