Which versions of lf295hgj2 are malicious?

The following RubyGems versions of lf295hgj2 are flagged malicious: 0.0.594067. Treat any of these as compromised.

How do I remediate lf295hgj2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lf295hgj2 (version 0.0.594067).

Malicious package

lf295hgj2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lf295hgj2 (RubyGems)

MAL-2026-7996

Immediate action

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

gem uninstall lf295hgj2

Malicious versions

1 flagged

0.0.594067

Indicators of compromise (SHA-256)

da0dbf9e516edd7c4af34115d5a0bc4fcb83fe37b39b79a856ead06dc582d6a0

bec1f07c266bee2b71fa5f4396ea3c6819528b09d17faa011a7a0cf28ff33c77

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02647RLUA-2026-08464

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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