Which versions of rxwandmeet are malicious?

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

How do I remediate rxwandmeet if I installed it?

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

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

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

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

Malicious package

rxwandmeetRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8555

Immediate action

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

gem uninstall rxwandmeet

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e97842ec1ccd1545d15ece69a795c5f0ebce3c01666bf6852452ac1193eb39b8

a4860f58ef784d8652b5735c8cd5501a5508cdf39a8d05780b676dcbe56179a9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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