Which versions of sb759e41fa are malicious?

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

How do I remediate sb759e41fa if I installed it?

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

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

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

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

Malicious package

sb759e41faRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8581

Immediate action

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

gem uninstall sb759e41fa

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9f5b2c3ca204a9587e14630283e80998e91ec129b26af01e61f713cb64dd9dd8

3c272bf5b84b1ec978fb118da2fb62ab5f88b8b81778edad4bcdbf356ff50f86

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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