Which versions of sf126006 are malicious?

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

How do I remediate sf126006 if I installed it?

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

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

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

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

Malicious package

sf126006RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8589

Immediate action

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

gem uninstall sf126006

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c84bfed0be0f03dde64010a701d99c96bf94865a9875502e8411dd3401cfb6fd

ec91085d70682d93492f57e97f93c48f337144fde968840fadd30a03f8d5b71a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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