Which versions of prxdfbdfbeb3b are malicious?

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

How do I remediate prxdfbdfbeb3b if I installed it?

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

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

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

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

Malicious package

prxdfbdfbeb3bRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8466

Immediate action

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

gem uninstall prxdfbdfbeb3b

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6fb1ad2c9e3891203b27bc188f2a4269f8f9e729c04ceb718000e75946dae28d

786d7cea403afba02d9bf041a17afc717c0c85e1e1157b658e92ad89a9e07193

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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