Which versions of sb50a0902f are malicious?

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

How do I remediate sb50a0902f if I installed it?

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

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

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

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

Malicious package

sb50a0902fRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8579

Immediate action

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

gem uninstall sb50a0902f

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

069c18571fa0f820549859c89f2ec1dece0807631aa26202b3596635f8204fbf

2546c62c28bfce73292acab769e21dc24e0b6f9495a797ff19d88f87228d1e0b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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