Which versions of xwandservmtg are malicious?

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

How do I remediate xwandservmtg if I installed it?

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

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

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

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

Malicious package

xwandservmtgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9547

Immediate action

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

gem uninstall xwandservmtg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e9a9d7898b13886232c7ef96511f95ad2ba820c7ca780efefcd37579d80c5148

9f927508bedeaedf74a8a3abda11bb9cfc56d439b532e53919505bbadaab0518

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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