Which versions of zpx52551xm are malicious?

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

How do I remediate zpx52551xm if I installed it?

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

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

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

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

Malicious package

zpx52551xmRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9691

Immediate action

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

gem uninstall zpx52551xm

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ac0a54c85d8b2c6393d0b107e28b74ee2b6ab4b19acf0e5310d6d994d431c3ef

d660c9521ce88940b50342d0b53ce55b02d4a040a928a54a17023be6e24428c4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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