Which versions of lambproxy4 are malicious?

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

How do I remediate lambproxy4 if I installed it?

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

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

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

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

Malicious package

lambproxy4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7825

Immediate action

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

gem uninstall lambproxy4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a99144cbc1eec177e53b764807fbb598464fb88930124692cbd0d2fe91de3130

6ccf01c35f742f8a4d7ae407814e9e501f6acd77a6f37e782945408c9efde1ee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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