Which versions of zpx52517nh are malicious?

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

How do I remediate zpx52517nh if I installed it?

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

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

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

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

Malicious package

zpx52517nhRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9681

Immediate action

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

gem uninstall zpx52517nh

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a3ae6e7f36dfab109e0b92ac6896eb2447e3500b9b408f54bed9353511e72885

b7fab42516a17560fb0ddbb3cc7aad371d0a41ddabeaabfab7fe9ca399d885de

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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