Which versions of lambproxy5 are malicious?

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

How do I remediate lambproxy5 if I installed it?

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

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

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

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

Malicious package

lambproxy5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7826

Immediate action

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

gem uninstall lambproxy5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b08f00d62bc42c041604748f586e21694a3556d53f830c6ec5a571ed287ee5f9

38211887309bb7a3908032c3925c3eb7a82acd4f21707464d723f1ada8b9a7d1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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