Which versions of lamhg57714 are malicious?

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

How do I remediate lamhg57714 if I installed it?

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

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

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

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

Malicious package

lamhg57714RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7863

Immediate action

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

gem uninstall lamhg57714

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d7a109a54ef62da7fe025a5c1fe2f75f9bd6dc9808531fbb6c5aec019c10dfca

51761caca3b34549ef2431afc0b4aafbea92239e72e994722bf991b868d8ac18

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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