Which versions of proxyt8be2d980 are malicious?

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

How do I remediate proxyt8be2d980 if I installed it?

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

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

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

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

Malicious package

proxyt8be2d980RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8444

Immediate action

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

gem uninstall proxyt8be2d980

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2a829af6c6b434e865c0e6fecb2746c325ac67faf70bc775c73e879caa849adc

f021de1590d76feeffbec03ed98755499a8860f9eff45ea7b93c915bebabe8a3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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