Which versions of dlpdf1734901 are malicious?

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

How do I remediate dlpdf1734901 if I installed it?

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

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

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

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

Malicious package

dlpdf1734901RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7615

Immediate action

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

gem uninstall dlpdf1734901

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

09bad1da4334a3eb94317d4b9065ff55ff95bebadaceb3762aa41ed4a39c752b

3833a105bc56d9bb5e379f38d4e80090c97a202fae20beee57cbdef34600841b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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