Which versions of lambqproxy are malicious?

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

How do I remediate lambqproxy if I installed it?

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

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

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

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

Malicious package

lambqproxyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7841

Immediate action

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

gem uninstall lambqproxy

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d38b3f37955878e069db90200d473f8cdb447b3ce1f9124613296444be1b9791

a39b4659b80f7fc9c1264696154a7516ed53adcb7744a3aa50fce56c1cf627c2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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