Which versions of zw_nobdr_events2 are malicious?

The following RubyGems versions of zw_nobdr_events2 are flagged malicious: 0.0.1340. Treat any of these as compromised.

How do I remediate zw_nobdr_events2 if I installed it?

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

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

Yes — zw_nobdr_events2 is associated with the RLMA-2026-04476, RLUA-2026-10414 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_events2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zw_nobdr_events2 (version 0.0.1340).

Malicious package

zw_nobdr_events2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zw_nobdr_events2 (RubyGems)

MAL-2026-9825

Immediate action

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

gem uninstall zw_nobdr_events2

Malicious versions

1 flagged

0.0.1340

Indicators of compromise (SHA-256)

97fcb320b491bad3253a5e49673056886a6e240a2d61e2b1c6d652f4e8092ec6

4db9da7b03f221d97d52c5e88fd25c47dad4e69fb7d3ae18aa411ec8946d69a6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04476RLUA-2026-10414

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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