Which versions of proxytf4d297de are malicious?

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

How do I remediate proxytf4d297de if I installed it?

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

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

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

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

Malicious package

proxytf4d297deRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8452

Immediate action

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

gem uninstall proxytf4d297de

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

76b0201ba1876868e5b115531055f29416dc3429907ea6ea68a34c21b54f81b5

fe337926286b5783a61482ab9cad4c49ec4785a36a90a866ce276195128937e6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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