Which versions of prx6cfa4a2be2 are malicious?

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

How do I remediate prx6cfa4a2be2 if I installed it?

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

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

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

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

Malicious package

prx6cfa4a2be2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8462

Immediate action

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

gem uninstall prx6cfa4a2be2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fb9f23b2ff3e741eb7f5f76c59f9db24abf67a977cafda716451def76ce09e54

db897aebef18cdde4f1a729f452ce2726727de4f5131d83911df5c8a9d9e3609

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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