Which versions of lambproxy2 are malicious?

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

How do I remediate lambproxy2 if I installed it?

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

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

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

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

Malicious package

lambproxy2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7823

Immediate action

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

gem uninstall lambproxy2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bc8cecee87981fae0f7f99ed46907f45d1df22d0bbdab3e5389b6620f9137e95

a42b8e379dda38a68a6a62c46dc735f29f28a09505336b5abfa11e1d585a5ee4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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