Which versions of sb01dc8349 are malicious?

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

How do I remediate sb01dc8349 if I installed it?

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

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

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

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

Malicious package

sb01dc8349RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8576

Immediate action

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

gem uninstall sb01dc8349

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

592884cca6f16e1ef62029b3cedc7975ddadca6a8c26ab17fc3c43e8cc652a95

ff178d7812c1dd90de9e63baf51c4548a2d0426d68ca81d0a717be40bf36c521

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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