Which versions of prx5a01811907 are malicious?

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

How do I remediate prx5a01811907 if I installed it?

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

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

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

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

Malicious package

prx5a01811907RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8461

Immediate action

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

gem uninstall prx5a01811907

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ab6d3f2953681c594c9ab75d3ce4ed6a0fd4121a3900f6fe7334c4f2e6f112cc

5980a89e66eb3a334a88c79f776d30441d01842ef378e5a13597a30f1c4f08b1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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