Which versions of sba517fb66 are malicious?

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

How do I remediate sba517fb66 if I installed it?

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

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

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

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

Malicious package

sba517fb66RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8582

Immediate action

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

gem uninstall sba517fb66

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3526646504a8eeaf3a751168ce927081e9cf1bc097f60a71125a81988f6b9d41

f20aac093dbb68344ed54bba4e4794aec81a450db4a5df31f9255a4f2eec31c1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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