Which versions of f2fe-s1 are malicious?

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

How do I remediate f2fe-s1 if I installed it?

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

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

Yes — f2fe-s1 is associated with the RLMA-2026-02334, RLUA-2026-08079 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 f2fe-s1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for f2fe-s1 (version 0.0.1).

Malicious package

f2fe-s1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

f2fe-s1 is a confirmed malicious RubyGems package (MAL-2026-7683) 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 f2fe-s1 (RubyGems)

MAL-2026-7683

Immediate action

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

gem uninstall f2fe-s1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7a827fed8f633ce969f6fee17435cdbc3f46118fc1877d2f50e273de18e86d9f

33050c9a6122fecc9e9a62a1203513e7a1210ed2144117d018ba1f2f56c9e006

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks f2fe-s1-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