Which versions of proxyt7f4a816d are malicious?

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

How do I remediate proxyt7f4a816d if I installed it?

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

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

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

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

Malicious package

proxyt7f4a816dRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8442

Immediate action

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

gem uninstall proxyt7f4a816d

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

61eb3c319bd8d3a16aaa047574c4d173f41f46eff6bcae36d5ec367777ceb5b7

3f35d547637ea5b5c3a1e1ac1266f1127c0cd06c07b2f44a24e7b5956ed30e2e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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