Which versions of proxylambethabc are malicious?

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

How do I remediate proxylambethabc if I installed it?

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

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

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

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

Malicious package

proxylambethabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8430

Immediate action

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

gem uninstall proxylambethabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5405dfc02887ba01314e22a41e5f68305fec4e3b5127e24032c361b31a5f3349

ebc12a676fa0a6244cd7dea52a889c35372cb6275fffd48586752d9688966b08

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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