Which versions of lambx6905360 are malicious?

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

How do I remediate lambx6905360 if I installed it?

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

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

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

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

Malicious package

lambx6905360RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7851

Immediate action

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

gem uninstall lambx6905360

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fef969377cdcf2efdbc0a1eede9710247221606b2420e38feab07f1cd2600818

82fcd712483f5bee10e019a3ca80bed2a16e5770c6b5df1e62a4ddf811695285

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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