Which versions of zpx52537th are malicious?

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

How do I remediate zpx52537th if I installed it?

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

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

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

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

Malicious package

zpx52537thRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9687

Immediate action

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

gem uninstall zpx52537th

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1eb3249d6b78272746c56052e4c6056e7b5a8faea00dc8fd3391dfc9030f164e

50163ef67e70bc81505ea4f8bb6bd07edbd530ebb4c9ef0b00e761cecd4a9347

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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