Which versions of proxyt8b7e7610 are malicious?

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

How do I remediate proxyt8b7e7610 if I installed it?

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

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

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

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

Malicious package

proxyt8b7e7610RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8443

Immediate action

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

gem uninstall proxyt8b7e7610

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

acaa0952347747c42ef76979fd02af45608e46ff17a1294c2428869cc39ec458

5b5000a7d90ea586cab1ddf1c9c67c9f5ad830709ac9a223d04c1dce4330faf6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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