Which versions of lambx1623642 are malicious?

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

How do I remediate lambx1623642 if I installed it?

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

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

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

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

Malicious package

lambx1623642RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7845

Immediate action

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

gem uninstall lambx1623642

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0cc5a988b5194e81f7a684c53531ec67f572a08fece44342ba2b617e9d195061

3cff785643ff516f4230de70fffffda1a9d0b3f9878913cef8454be114ba125f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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