Which versions of zpx52530rm are malicious?

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

How do I remediate zpx52530rm if I installed it?

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

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

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

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

Malicious package

zpx52530rmRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9685

Immediate action

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

gem uninstall zpx52530rm

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

54f280bb1828e2da1b83dcfdac642aadd20143290d10c7d799e2b78491dd3986

ce969539fa8f22a72d89897f245e5ab7c4f276c0eb0ad42ec559d9679b08f3e7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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