Which versions of lpdfdev8687 are malicious?

The following RubyGems versions of lpdfdev8687 are flagged malicious: 0.0.68687. Treat any of these as compromised.

How do I remediate lpdfdev8687 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lpdfdev8687 (version 0.0.68687).

Malicious package

lpdfdev8687RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lpdfdev8687 (RubyGems)

MAL-2026-8048

Immediate action

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

gem uninstall lpdfdev8687

Malicious versions

1 flagged

0.0.68687

Indicators of compromise (SHA-256)

1203bda8d29690e4e436d7b2bbeb1fa63dfc54ca9319f526ce6ebaba92e3ba53

5883674d5408677f857e3343331fda6ac27fe2f453dcd31fcaaf7f4dc0819ef1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02699RLUA-2026-08547

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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