Which versions of lpp29938 are malicious?

The following RubyGems versions of lpp29938 are flagged malicious: 0.0.69938. Treat any of these as compromised.

How do I remediate lpp29938 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lpp29938 (version 0.0.69938).

Malicious package

lpp29938RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lpp29938 (RubyGems)

MAL-2026-8051

Immediate action

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

gem uninstall lpp29938

Malicious versions

1 flagged

0.0.69938

Indicators of compromise (SHA-256)

fcaa172b7714784bcb9ce8a2d974090a0c56873e7fff88a4c05e4b0063fc9193

be1484a02ca2462ac73892e8b683a4b4313df26b164507d4e2dfc895421f8ced

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02702RLUA-2026-08550

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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