Which versions of rxwandjan are malicious?

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

How do I remediate rxwandjan if I installed it?

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

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

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

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

Malicious package

rxwandjanRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8554

Immediate action

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

gem uninstall rxwandjan

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6ad68b598fa10590c0355282402765b2529cd7d3a749815218cafcc662970507

bf16508d9fefc3478da6a5246c1e2eb34554140f401d1bd22875890a38a3909e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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