Which versions of rxsjq are malicious?

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

How do I remediate rxsjq if I installed it?

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

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

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

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

Malicious package

rxsjqRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8550

Immediate action

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

gem uninstall rxsjq

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b2915cb3e7ccf66df0c5c6c6b96559d0b503cd208d6142a7f082bdec59d52f9a

af8556e419be02ee1f60f9c13fe0fe5485525543a45c9f74233787b77c72d8fa

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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