Which versions of zzwmgweb02 are malicious?

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

How do I remediate zzwmgweb02 if I installed it?

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

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

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

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

Malicious package

zzwmgweb02RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-10004

Immediate action

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

gem uninstall zzwmgweb02

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7c03701cabfc8cc50b4065f30638756da79fa68da0b93d230835ed2b02d04bca

39f2a4196dcca17c33fcac546d9c00bb30c2a017dafaa8228281cd4b53cb62ef

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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