Which versions of zpx52477bh are malicious?

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

How do I remediate zpx52477bh if I installed it?

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

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

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

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

Malicious package

zpx52477bhRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9669

Immediate action

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

gem uninstall zpx52477bh

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d40b08b55447d5a318045f40a4a5927ef83249924dc070c2ecb82265433f8d6d

97502ade6b6f6775b7509dac74a6fe327936ff37dd8d7ea8f02b065b876c68e4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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