Which versions of lamhack1778555394 are malicious?

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

How do I remediate lamhack1778555394 if I installed it?

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

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

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

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

Malicious package

lamhack1778555394RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7862

Immediate action

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

gem uninstall lamhack1778555394

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

95df6138cd2fbfc81dafeebc5d235a5fd5f43fc696155c851a71fa04754a17f0

a18d5765ec9b46c8d9eae7462ca58306a6685c4aee42b9d9464017f3f4757ef1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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