Which versions of pdfkent1 are malicious?

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

How do I remediate pdfkent1 if I installed it?

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

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

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

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

Malicious package

pdfkent1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8421

Immediate action

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

gem uninstall pdfkent1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c1ba3aad9c3ad7ebc4b3148d731d14f793daf201aa8ec4d82cd6960fe2f5e7f9

c0c88f840ae7cbf9064aba8df277fa1315f38710a345a8cc756c057956826c04

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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