Which versions of lambegitx4062 are malicious?

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

How do I remediate lambegitx4062 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lambegitx4062 (2 malicious versions).

Malicious package

lambegitx4062RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lambegitx4062 is a confirmed malicious RubyGems package (MAL-2026-7788) that executes malicious code on install (malicious versions 0.0.1, 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lambegitx4062 (RubyGems)

MAL-2026-7788

Immediate action

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

gem uninstall lambegitx4062

Malicious versions

2 flagged

0.0.10.0.3

Indicators of compromise (SHA-256)

99bd20283ed4a8e3d9836ea79e4677f070a907686829df6984072cb13d4df016

faed874908f38bee8aa0af795f50bff5c0c6f1c8cf4e04aa1906cf2fb57ab6e4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lambegitx4062 (2 malicious versions).
If you installed it — respond
Remove lambegitx4062 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 lambegitx4062 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. lambegitx4062 on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02446RLUA-2026-08261

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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