Which versions of proxyt18c96c16 are malicious?

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

How do I remediate proxyt18c96c16 if I installed it?

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

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

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

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

Malicious package

proxyt18c96c16RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8438

Immediate action

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

gem uninstall proxyt18c96c16

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d9eb839ce31539a8e1f61340cf5b8ffa321833a0f91613bc8ed8961d5890d245

ec2caf4e862d7788b0b738bbfa2bfab0e31804a3e666aae244204b30017d3bfd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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