Which versions of prx06e608f6da are malicious?

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

How do I remediate prx06e608f6da if I installed it?

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

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

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

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

Malicious package

prx06e608f6daRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8455

Immediate action

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

gem uninstall prx06e608f6da

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

91d78eabde617e2fbc71e91838fc7bdf2cc840286c6b5dd8d8c32a7a5068ec02

ef238e2cbfe51177dde0ded57094e28d08195a6b269000f3114fede2fa6dccfb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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