Which versions of lambehgnew1593 are malicious?

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

How do I remediate lambehgnew1593 if I installed it?

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

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

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

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

Malicious package

lambehgnew1593RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7789

Immediate action

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

gem uninstall lambehgnew1593

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

713ca34eda78a242d386744291663d5ab90393aacd75ebfd099ad035b9507650

ad3da79da44c873bb12ab81a811b317d8c5b69ac33ef9796e319521cbc8779aa

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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