Which versions of zwmeet017694 are malicious?

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

How do I remediate zwmeet017694 if I installed it?

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

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

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

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

Malicious package

zwmeet017694RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9892

Immediate action

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

gem uninstall zwmeet017694

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5ffea44fcd2f04a9703915b49f2c5e4426242a1136b4b77b70396f66ba0c5f56

de61206dd5c0d4ef4bfc630d9bc23ca85a41c5e9c3fa75de582048f439f734de

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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