Which versions of prx92ddbfc4c5 are malicious?

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

How do I remediate prx92ddbfc4c5 if I installed it?

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

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

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

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

Malicious package

prx92ddbfc4c5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8463

Immediate action

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

gem uninstall prx92ddbfc4c5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2d7bfb339f42e04bffed35aea5947d32534a1ea063071f5b4aa480079dbc0cff

39b7311610c50b01abab1743c2bf4aecc6baf938257163437df5b038af6ec680

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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