Which versions of lambpx26687 are malicious?

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

How do I remediate lambpx26687 if I installed it?

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

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

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

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

Malicious package

lambpx26687RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lambpx26687 (RubyGems)

MAL-2026-7832

Immediate action

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

gem uninstall lambpx26687

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

620900f8e23a08a998a4a1e336e74eeb30593499d945261878805234ca6b576d

d7f041e4a208863c67048c473e7ee53e018fb1f63b0cf45c912f78b3ad9f08e4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02490RLUA-2026-08305

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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