Which versions of sf1d68a9 are malicious?

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

How do I remediate sf1d68a9 if I installed it?

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

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

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

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

Malicious package

sf1d68a9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8590

Immediate action

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

gem uninstall sf1d68a9

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

25d03b671fcec6ee16e0ae5ee998dfcd37ae203b1ae27b94f507f348a12acf37

7488ca05c1eecf06dbe7ee5ba08d8a1529517d68e6a48a67db60ba70658e641f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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