Which versions of zpx52500is are malicious?

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

How do I remediate zpx52500is if I installed it?

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

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

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

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

Malicious package

zpx52500isRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9676

Immediate action

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

gem uninstall zpx52500is

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d828f096d86d34afe5e90e39099bf34c3fbe1e1f3a8c9ff8d7b70716b65056bc

7886d0624f1a6959fe91a84d6e1fb8fec62f2612578bf73a7d65aac39f7d6e3a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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