Which versions of lp125 are malicious?

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

How do I remediate lp125 if I installed it?

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

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

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

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

Malicious package

lp125RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lp125 is a confirmed malicious RubyGems package (MAL-2026-8032) 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 lp125 (RubyGems)

MAL-2026-8032

Immediate action

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

gem uninstall lp125

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5a50503aef38159ba7f09047e545b1074d98f457ba8e4ef39770ae3efc64f90b

ef6dcf4a103227251843bfdda70903107d4aee6b932230a9b2ec9ad358619174

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lp125 (version 0.0.1).
If you installed it — respond
Remove lp125 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 lp125 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. lp125 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-02683RLUA-2026-08531

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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