Which versions of lambproxy1 are malicious?

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

How do I remediate lambproxy1 if I installed it?

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

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

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

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

Malicious package

lambproxy1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7822

Immediate action

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

gem uninstall lambproxy1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1c6fc147a3313497428c3239ec144679f1be4a51cb5e1f5410162554a28cff6b

ee078d1a95170ff9ea6d5beac93059adf9659ddca5138c649d91907e831b4894

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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