Which versions of lf295s3 are malicious?

The following RubyGems versions of lf295s3 are flagged malicious: 0.0.894635. Treat any of these as compromised.

How do I remediate lf295s3 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295s3 (version 0.0.894635).

Malicious package

lf295s3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295s3 (RubyGems)

MAL-2026-8019

Immediate action

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

gem uninstall lf295s3

Malicious versions

1 flagged

0.0.894635

Indicators of compromise (SHA-256)

ae1d70543328ab2a60ff51dd97318152f47a4afa119acca9c0bcca5aa9f88d50

7531a323e3f272e4bcaae2af7342e4e9ff1b5bd1a6878cef55c105dab2374bec

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02670RLUA-2026-08487

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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