Which versions of grpdf1 are malicious?

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

How do I remediate grpdf1 if I installed it?

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

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

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

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

Malicious package

grpdf1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7722

Immediate action

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

gem uninstall grpdf1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5ccb5f46b5fa321bfcbbbdc17c9bca75a430106f3740120b104e1c3d621a55c0

37295be6df4ebdc70a3849f950115b7a895ff16d0c3adc97f23a06929521972d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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