Which versions of lambproxyfetchx are malicious?

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

How do I remediate lambproxyfetchx if I installed it?

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

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

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

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

Malicious package

lambproxyfetchxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7828

Immediate action

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

gem uninstall lambproxyfetchx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e89f8ff2f5288e6584008974b80016de6a52150d77079f11ef957bc917488fd6

b4a316ddc192aa1d863c3d0e9269bc8b62b9d5c54caa770ffcd6b89a99145668

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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