Which versions of prx48d92bd9a6 are malicious?

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

How do I remediate prx48d92bd9a6 if I installed it?

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

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

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

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

Malicious package

prx48d92bd9a6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8459

Immediate action

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

gem uninstall prx48d92bd9a6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8a8cfa3b23254d2a61fceee4bbbd51ee7d717b73088ba92704eb5191991540aa

8147861c04e254e0ffb1e70233c3759f80bcad1dca5336155f10fbc5747e1300

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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