Which versions of sb70efdeba are malicious?

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

How do I remediate sb70efdeba if I installed it?

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

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

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

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

Malicious package

sb70efdebaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8580

Immediate action

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

gem uninstall sb70efdeba

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

efc994bc8c0930309890659fbd3a1a253e4f5c1427f1e3b744779e5ee41b7fcd

259384f8a5b104aff7170c676ca548f30a71882edebc2f61b664e7a877fa585a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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