Which versions of prxe87db1bbc7 are malicious?

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

How do I remediate prxe87db1bbc7 if I installed it?

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

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

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

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

Malicious package

prxe87db1bbc7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8467

Immediate action

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

gem uninstall prxe87db1bbc7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dbb337046f6f384fd93f1e4145d7edfcbc993dbc262329be2ee877a9c3d61b5e

6932586b6e4b26171f0ecb960f16797eae9cb59102d4aeae78d6524ada1c1f35

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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