Which versions of prx51cee8dbf7 are malicious?

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

How do I remediate prx51cee8dbf7 if I installed it?

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

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

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

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

Malicious package

prx51cee8dbf7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8460

Immediate action

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

gem uninstall prx51cee8dbf7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

da2b30864125315e44bfde2f69a1bffbdf4cbf7bb1f3b534cca0deb5c8981c77

be1f4a3396107b7bd37ac0416c35c7cc4bb3a8a4bbc111af31fc13122c91e4e1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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