Which versions of steelproxymod are malicious?

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

How do I remediate steelproxymod if I installed it?

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

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

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

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

Malicious package

steelproxymodRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8905

Immediate action

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

gem uninstall steelproxymod

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

18f3dfa719c1f42e8cac4b4dc731e75bf152f2e654dcf6be08bfbefa0b4f1cca

778e92764874b35f7d2cd1106a3256f1bd05b91dc6aaddd50765fb0bd980b121

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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