Which versions of prxca79e95716 are malicious?

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

How do I remediate prxca79e95716 if I installed it?

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

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

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

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

Malicious package

prxca79e95716RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8465

Immediate action

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

gem uninstall prxca79e95716

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1f35e2ab2b970a4c8aa652379dff3491eb6f3043c54dc6bc42180007ddd7e797

48c562d11c9ade82dff6ba2a122ed02fe35aa7b70a5a11dd768ce3504316bfec

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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