Which versions of sf72647c are malicious?

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

How do I remediate sf72647c if I installed it?

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

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

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

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

Malicious package

sf72647cRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8593

Immediate action

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

gem uninstall sf72647c

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b4fa3ebe9cc5f30cde31fc8a8ed1488396a793d14d088c77c73fa422e4c548d1

2ecc961eda3d619551108ad1307e2e8dd8997f55771ee0cb87a8921cc1027abf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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