Which versions of lf295q6 are malicious?

The following RubyGems versions of lf295q6 are flagged malicious: 0.0.786455. Treat any of these as compromised.

How do I remediate lf295q6 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295q6 (version 0.0.786455).

Malicious package

lf295q6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lf295q6 is a confirmed malicious RubyGems package (MAL-2026-8009) that executes malicious code on install (malicious version 0.0.786455). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lf295q6 (RubyGems)

MAL-2026-8009

Immediate action

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

gem uninstall lf295q6

Malicious versions

1 flagged

0.0.786455

Indicators of compromise (SHA-256)

10c8e9da126e2edc09d1e0ca3ef1dab1064acd349cac9cf8bc3fdfeae72c2562

5c9606c0aba29ac8f2b3993d6d0d2f77704d8510202e0cda0ee7957f7152878f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02660RLUA-2026-08477

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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