Which versions of lambproxyx are malicious?

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

How do I remediate lambproxyx if I installed it?

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

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

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

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

Malicious package

lambproxyxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7831

Immediate action

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

gem uninstall lambproxyx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7400022479b83ce998f21760de7ff8a9d2b7736a13fd46b2dcd9d8e76481cf2c

baaf9679eabe9036fc3bbc8805c60fd146e36f6053fbe894d272507a61d8d952

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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