Which versions of proxytcf1f8d7b are malicious?

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

How do I remediate proxytcf1f8d7b if I installed it?

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

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

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

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

Malicious package

proxytcf1f8d7bRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8449

Immediate action

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

gem uninstall proxytcf1f8d7b

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

86a1b2a954a3558af8741b4bb20ea2c0e6a5783053a76dfac8dcc1f70699dd18

8b564eaa94dca1923ca320f9ff54e1f1f68c0780cb68dbc164e33da94f04623f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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