Which versions of zpx52483db are malicious?

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

How do I remediate zpx52483db if I installed it?

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

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

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

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

Malicious package

zpx52483dbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9671

Immediate action

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

gem uninstall zpx52483db

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

720f8507b9d818a1d4c3b230a1d021bc076498c48fead13a4b8a32306207b662

a246828fc2643a05cc0fb42b7d761a2befabb6ee02e116bf046eb9f1ede4d4cf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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