Which versions of zw_nobdr_events are malicious?

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

How do I remediate zw_nobdr_events if I installed it?

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

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

Yes — zw_nobdr_events is associated with the RLMA-2026-04475, RLUA-2026-10413 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_events across my projects, lockfiles, and CI pipelines?

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

Malicious package

zw_nobdr_eventsRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zw_nobdr_events is a confirmed malicious RubyGems package (MAL-2026-9824) 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_events (RubyGems)

MAL-2026-9824

Immediate action

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

gem uninstall zw_nobdr_events

Malicious versions

1 flagged

0.0.1339

Indicators of compromise (SHA-256)

1249e91680c633bb398be3f0ca122bc0833938b548ea2a430ee88312924075f1

e694f6a578a73759ad643f25dfff2ef62196a3561f0c6364cc48df1b24e329fd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zw_nobdr_events (version 0.0.1339).
If you installed it — respond
Remove zw_nobdr_events 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_events 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_events 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-04475RLUA-2026-10413

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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