Which versions of sbc55dd196 are malicious?

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

How do I remediate sbc55dd196 if I installed it?

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

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

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

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

Malicious package

sbc55dd196RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8583

Immediate action

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

gem uninstall sbc55dd196

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

356b3dbf0a518420c26b4a221b877709332727ac9506a088fa7008baa49b6435

5df21c4cadea345cb47b4e70aa86db066e4da0c317ff70024408d8de365790a0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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