Which versions of proxytf0ccd93e are malicious?

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

How do I remediate proxytf0ccd93e if I installed it?

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

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

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

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

Malicious package

proxytf0ccd93eRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8451

Immediate action

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

gem uninstall proxytf0ccd93e

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

891937541a64a60809bffc89e617cb8a92253d5039af623a5ec9b7b3d5f081a3

33b3693612cc61d32e3050c5cebf5dabab7976c0404425a33c743867fa1fe947

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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