Which versions of zw_nobdr_day are malicious?

The following RubyGems versions of zw_nobdr_day are flagged malicious: 0.0.1338. Treat any of these as compromised.

How do I remediate zw_nobdr_day if I installed it?

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

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

Yes — zw_nobdr_day is associated with the RLMA-2026-04472, RLUA-2026-10410 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_day across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zw_nobdr_day (version 0.0.1338).

Malicious package

zw_nobdr_dayRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zw_nobdr_day (RubyGems)

MAL-2026-9821

Immediate action

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

gem uninstall zw_nobdr_day

Malicious versions

1 flagged

0.0.1338

Indicators of compromise (SHA-256)

62b571d5f8019c19b23f0d962a5e3b8864583b8c2e252f3e3ac65c414013bfe7

4671f9c62d2bd812753c97cb94f2ac56b80cf9f2436c7163e18293c89a2cdb1b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04472RLUA-2026-10410

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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