Which versions of zzdelay2119 are malicious?

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

How do I remediate zzdelay2119 if I installed it?

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

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

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

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

Malicious package

zzdelay2119RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9935

Immediate action

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

gem uninstall zzdelay2119

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

948e93cb739fa4e5d469f89cefb51809acf64c5732145d1cb58bd0a855f722ac

7ad13acea7712d71bad3a2775f21ab773c9959d5a1b06ede399ac0aaf62f6a8d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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