Which versions of redis_connectable are malicious?

The following RubyGems versions of redis_connectable are flagged malicious: 90002.0. Treat any of these as compromised.

How do I remediate redis_connectable if I installed it?

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

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

Yes — redis_connectable is associated with the RLMA-2025-06626, RLUA-2026-09030 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 redis_connectable across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for redis_connectable (version 90002.0).

Malicious package

redis_connectableRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

redis_connectable is a confirmed malicious RubyGems package (MAL-2025-192916) that executes malicious code on install (malicious version 90002.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in redis_connectable (RubyGems)

MAL-2025-192916

Immediate action

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

gem uninstall redis_connectable

Malicious versions

1 flagged

90002.0

Indicators of compromise (SHA-256)

7ba50847315a286e79b66928405eb681a0ea56cfc81d610d96045a87ce6bcb51

a44608ad105cb7ef30b6a8a2ff4ca5a33b81339a1c2db60426bc0b8e996a4130

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for redis_connectable (version 90002.0).
If you installed it — respond
Remove redis_connectable 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 redis_connectable 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. redis_connectable on RubyGems has been identified as a malicious package (version 90002.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06626RLUA-2026-09030

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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