Which versions of proxyt8c6730c3 are malicious?

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

How do I remediate proxyt8c6730c3 if I installed it?

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

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

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

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

Malicious package

proxyt8c6730c3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8445

Immediate action

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

gem uninstall proxyt8c6730c3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

210684f479cd4b6882586042dcd270d232798707ac93b7940bc4a0a388754151

97eaab847077ea9a543c0b99b9243dd227abad9f9216b77356e2cfc3df76d0dd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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