Which versions of fadtestgemx1 are malicious?

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

How do I remediate fadtestgemx1 if I installed it?

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

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

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

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

Malicious package

fadtestgemx1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7684

Immediate action

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

gem uninstall fadtestgemx1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fd8c1a44c9ffe6ebe01b1ff047651974cf05ebe15a2591a72e2ae998076d4fef

d550ba5dd810b6234e5f8ffb6f25c31355ea8a3b3b68e1a2f96691389f7d7431

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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