Which versions of lf295q10 are malicious?

The following RubyGems versions of lf295q10 are flagged malicious: 0.0.883567. Treat any of these as compromised.

How do I remediate lf295q10 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295q10 (version 0.0.883567).

Malicious package

lf295q10RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295q10 (RubyGems)

MAL-2026-7999

Immediate action

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

gem uninstall lf295q10

Malicious versions

1 flagged

0.0.883567

Indicators of compromise (SHA-256)

37a2255433eae9cc86d55b0ded172c8678a04491405b80c21ca2c5a7b5f7de50

e5e306c4a44235c67862df878a8af45ce2111c2f8f11418927eac7053305f429

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02650RLUA-2026-08467

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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