Which versions of xwandrss1 are malicious?

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

How do I remediate xwandrss1 if I installed it?

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

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

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

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

Malicious package

xwandrss1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9545

Immediate action

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

gem uninstall xwandrss1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

51fc222739ed3f7fd33835311e64ae41d983a9fa91917e5e01b87cb9058de7da

1820baddf13c42b911f79a41c9e198c6c3e6b908b17220ec4dad973504f9582d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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