Which versions of proxyt5d33dbc8 are malicious?

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

How do I remediate proxyt5d33dbc8 if I installed it?

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

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

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

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

Malicious package

proxyt5d33dbc8RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8440

Immediate action

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

gem uninstall proxyt5d33dbc8

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

104c8d248944579ef4b611bef3fd6a5077d7adb712c7e0fba418a17bc96f2fee

55981b0eb3fa8b940b98ce57da3872794ea9b588258a3bded9f50e6f06e96e16

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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