Which versions of lambhgampxyz are malicious?

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

How do I remediate lambhgampxyz if I installed it?

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

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

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

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

Malicious package

lambhgampxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7806

Immediate action

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

gem uninstall lambhgampxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

428b6d47efd8423259da823edbde29570465957866d99811bb1716b5075936d3

0e40f5baadd3e28414311941e781ffaad059ee0ffb89df13bdb656ef49846791

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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