Which versions of zpx52514mg are malicious?

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

How do I remediate zpx52514mg if I installed it?

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

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

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

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

Malicious package

zpx52514mgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9680

Immediate action

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

gem uninstall zpx52514mg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

529651a47706301631ddeba365e1c952ebacd539e3a01156feeac6759bdd8301

870a2eab2071fb9fe13f9c222d5049d2edc376124777da89a2527455d6acabc6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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