Which versions of proxyta14c1bf1 are malicious?

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

How do I remediate proxyta14c1bf1 if I installed it?

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

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

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

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

Malicious package

proxyta14c1bf1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8446

Immediate action

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

gem uninstall proxyta14c1bf1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

35f100275d2ac9aaaeb7997f77aa71082000af722c1f694b0cdbe29682d37f53

2d56dbd97d6169dce4ce94f1c93a11aee4c30cc858ecbedd0a54dfa8fb48942d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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