Which versions of sf3481c8 are malicious?

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

How do I remediate sf3481c8 if I installed it?

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

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

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

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

Malicious package

sf3481c8RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8591

Immediate action

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

gem uninstall sf3481c8

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ff8b7174c62b02f1033d8460bf23e35c1b3c133c25208534926695b9b642e3eb

d963e9d7d54435e4143c8e886cb1df8bb334ef93499be7dcc490f41465a12766

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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