Which versions of zpx52503jb are malicious?

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

How do I remediate zpx52503jb if I installed it?

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

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

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

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

Malicious package

zpx52503jbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9677

Immediate action

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

gem uninstall zpx52503jb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

af39f53096f4f6d92684ef1fcb9852ad4fdd1082e10292cb97559ffa3526f0c4

783896caa9cd608cc577a4434066e90b1d46c048f75af802a7a75140b0f8eee4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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