Which versions of lf295q13 are malicious?

The following RubyGems versions of lf295q13 are flagged malicious: 0.0.916436. Treat any of these as compromised.

How do I remediate lf295q13 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295q13 (version 0.0.916436).

Malicious package

lf295q13RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295q13 (RubyGems)

MAL-2026-8002

Immediate action

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

gem uninstall lf295q13

Malicious versions

1 flagged

0.0.916436

Indicators of compromise (SHA-256)

a379c82509c82ed87c9fab572470bd6562e7cae794b5110f1f2ea98adb15108b

cd3ca527d4cfa3eeaa196c2b598541c0b72f1fc6e54bc13e16d8e21ea31c5710

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02653RLUA-2026-08470

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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