Which versions of steelproxycab are malicious?

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

How do I remediate steelproxycab if I installed it?

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

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

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

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

Malicious package

steelproxycabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8904

Immediate action

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

gem uninstall steelproxycab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f8222667918643cdc22b4f1d0b1c2782411b4b86961f0c7e626143e6a0cda41f

3debb81cc3a2f852eb564e3e5c20a0c1a0d5d0b5839f9bed663b3aa39c00b05f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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