Which versions of lamhgip123959 are malicious?

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

How do I remediate lamhgip123959 if I installed it?

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

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

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

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

Malicious package

lamhgip123959RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7865

Immediate action

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

gem uninstall lamhgip123959

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

64233c1ee7d4839c620586da94a0993fc8c063a94153ebded951cd5f49c82991

3731d685d4b74a32032fccc7d1086d9e8e5cb6a815ab16b86d4b9192f908962c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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