Which versions of sb06ac4700 are malicious?

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

How do I remediate sb06ac4700 if I installed it?

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

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

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

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

Malicious package

sb06ac4700RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8577

Immediate action

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

gem uninstall sb06ac4700

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

19808aa6948761e8943081b472d7dba94bc3cc32b2fe107acd753c35b7668da3

3088a88bd93a0eb6b86c7f8b367254aa5e63a81a1fe7d39fa3e8ea1013d5b729

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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