Which versions of lambx6561211 are malicious?

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

How do I remediate lambx6561211 if I installed it?

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

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

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

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

Malicious package

lambx6561211RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7850

Immediate action

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

gem uninstall lambx6561211

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9f1de59052b8d98b5a828276987637c13591f2881588bca9cb8e6aac28e003ac

618101da517b29ab54b208d32289f576819ecefd8186116d03835078a3cd29db

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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