Which versions of proxyta4d404a4 are malicious?

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

How do I remediate proxyta4d404a4 if I installed it?

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

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

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

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

Malicious package

proxyta4d404a4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8447

Immediate action

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

gem uninstall proxyta4d404a4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

829cc47e5fc96bcde2ea77db12f8ad52ade097fac5d65a08729a92e3f25dd6bf

27ab06714efb9db4705b925ec54f6d9d7f97de39983c69874eb79ed66166db5b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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