Which versions of rxljq are malicious?

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

How do I remediate rxljq if I installed it?

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

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

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

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

Malicious package

rxljqRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8548

Immediate action

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

gem uninstall rxljq

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c49f6a8957679871d64d845660f47a5cbbbffcec8fa067c8d1cc210cad89e0cc

cad5df22938831f380bb88ad5f7533e968fa9a7f9ef9ad16ad90a1d1df1482f6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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