Which versions of ffxnzzez0bc are malicious?

The following RubyGems versions of ffxnzzez0bc are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate ffxnzzez0bc if I installed it?

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

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

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

Search your lockfiles and build artifacts for ffxnzzez0bc (3 malicious versions).

Malicious package

ffxnzzez0bcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

ffxnzzez0bc is a confirmed malicious RubyGems package (MAL-2026-7685) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ffxnzzez0bc (RubyGems)

MAL-2026-7685

Immediate action

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

gem uninstall ffxnzzez0bc

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

a80bc390d77fe3f1925e7a085067250ed03814ecda60d838c557a6e7d17cb03e

2dd90c62536686970a379170f6dce1d4613c21bdc36ee202d61b122cde30e0ca

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ffxnzzez0bc (3 malicious versions).
If you installed it — respond
Remove ffxnzzez0bc 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 ffxnzzez0bc 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. ffxnzzez0bc on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02336RLUA-2026-08081

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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