Which versions of lambproxya are malicious?

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

How do I remediate lambproxya if I installed it?

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

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

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

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

Malicious package

lambproxyaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7827

Immediate action

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

gem uninstall lambproxya

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5fc1f6c7ad6451b9665aa8021eee84853056513076169d93f17f28696d928fbe

4946944015ccf64411f8b4a2f6e91cb997f9b71be0e77cbffecd0874233aaedb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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