Which versions of zmodb4045 are malicious?

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

How do I remediate zmodb4045 if I installed it?

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

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

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

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

Malicious package

zmodb4045RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9665

Immediate action

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

gem uninstall zmodb4045

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0592becdf52e7971da15f86db3714e3d171a9e9cc2d1b3da65e8f4973c1e35da

9e0037e62827fd67723bae8bd0186857559946ce42bccb180c63fb46faf4af2c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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