Which versions of lpp19932 are malicious?

The following RubyGems versions of lpp19932 are flagged malicious: 0.0.69932. Treat any of these as compromised.

How do I remediate lpp19932 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lpp19932 (version 0.0.69932).

Malicious package

lpp19932RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lpp19932 (RubyGems)

MAL-2026-8050

Immediate action

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

gem uninstall lpp19932

Malicious versions

1 flagged

0.0.69932

Indicators of compromise (SHA-256)

239051b3b0d599a09ff205da4d41e65a86ff6fb8ec6163c643a4ceaf066f951c

7da2f7e4a9c4a506da1c402708a6118cd553fbbe7ecf6ca57babf014961a5dc9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02701RLUA-2026-08549

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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