Which versions of proxyt1ef3994c are malicious?

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

How do I remediate proxyt1ef3994c if I installed it?

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

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

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

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

Malicious package

proxyt1ef3994cRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8439

Immediate action

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

gem uninstall proxyt1ef3994c

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3640f829678e46af0ec83f84674b2c74f50ec06c1c355b8dc9b8893def922685

ec9cf37828fac98b5075a630e36bbe92c1daa7e15c62caf1e879a055726e81c0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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