Which versions of zw_nobdr_day2 are malicious?

The following RubyGems versions of zw_nobdr_day2 are flagged malicious: 0.0.1339. Treat any of these as compromised.

How do I remediate zw_nobdr_day2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zw_nobdr_day2 (version 0.0.1339).

Malicious package

zw_nobdr_day2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zw_nobdr_day2 is a confirmed malicious RubyGems package (MAL-2026-9822) that executes malicious code on install (malicious version 0.0.1339). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zw_nobdr_day2 (RubyGems)

MAL-2026-9822

Immediate action

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

gem uninstall zw_nobdr_day2

Malicious versions

1 flagged

0.0.1339

Indicators of compromise (SHA-256)

89678cf0d0fd74970c3910d3c491c1134776d45a2d5cc770a25a0edba29d13bf

ffedbbd171d2c7158f0cea0b9e13eef49cbe5a2d258dc8b2b51f47d95434e638

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zw_nobdr_day2 (version 0.0.1339).
If you installed it — respond
Remove zw_nobdr_day2 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 zw_nobdr_day2 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. zw_nobdr_day2 on RubyGems has been identified as a malicious package (version 0.0.1339 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04473RLUA-2026-10411

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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