Which versions of lambx5165217 are malicious?

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

How do I remediate lambx5165217 if I installed it?

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

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

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

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

Malicious package

lambx5165217RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7848

Immediate action

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

gem uninstall lambx5165217

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

34014489fbc62e57f584b1793bb010cea8b0c6eed84eccca40d8f14dfd0a7ec1

dbf3239b09a0dccb2b6c48bdd1024066312c57ccc06100f00c96244ae3d8a8c7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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