Which versions of lp357 are malicious?

The following RubyGems versions of lp357 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate lp357 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lp357 (version 0.0.1).

Malicious package

lp357RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lp357 (RubyGems)

MAL-2026-8042

Immediate action

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

gem uninstall lp357

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

99e6ccbc3f035b2cd2bbf05e98758904b870781aa488f51ffff8ab7bea39d942

51e3ebc4a715f10b96a9d6923c2afa26d91f6d8df14038a463a197c3b2717e59

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02693RLUA-2026-08541

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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