Which versions of prx4542f26b08 are malicious?

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

How do I remediate prx4542f26b08 if I installed it?

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

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

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

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

Malicious package

prx4542f26b08RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8458

Immediate action

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

gem uninstall prx4542f26b08

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b4c669af617562c7626a1d1ad3b2d7d9409bca11f02d9b21b66f96615524f4d7

cbd06ca5e92a56e3dc537f02bad74eff014475efd663be69941ab4f3afccb0fd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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