Which versions of proxyfooabc53ee9f5f are malicious?

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

How do I remediate proxyfooabc53ee9f5f if I installed it?

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

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

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

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

Malicious package

proxyfooabc53ee9f5fRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8429

Immediate action

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

gem uninstall proxyfooabc53ee9f5f

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c9ec4a3cde5d2f601132cfcb77fd16862cd90b8ef65c661aa38384f9c7e09ea4

12afe0714658778349e9e15a3ce0d2b1a0847cc599a2f49d74f1175fd6d78253

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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