Which versions of xwandstestfoobarx are malicious?

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

How do I remediate xwandstestfoobarx if I installed it?

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

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

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

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

Malicious package

xwandstestfoobarxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9548

Immediate action

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

gem uninstall xwandstestfoobarx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

072898c89eb5b7acafd1f7b8c53c97f39d97833110f819c1737871082062d275

890b9e929ff1a2c605ef261cf9b66ac5a58e60c2c128af7cf98b4d6f5f5c7c92

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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