pdf-lib-enhancednpm
Advisory published Updated
pdf-lib-enhanced is a confirmed malicious npm package (MAL-2026-4799) that steals credentials and exfiltrates sensitive data (malicious version 2.2.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pdf-lib-enhanced (npm)
What this malware does
Package name pdf-lib-enhanced mimics the widely-used pdf-lib library and ships a verbatim copy of upstream's README. package.json declares repository.url pointing at a fresh GitHub account (harunosakura030303-maker/pdf-lib-enhanced) while bugs.url still points at the original Hopding/pdf-lib project — a metadata mismatch consistent with a hastily-forked squat. The dist/ directory contains unrelated SheetJS assets (xlsx.full.min.js, xlsx.zahl.js, cpexcel.js, etc.) that have no purpose in a PDF library. However, the CommonJS main entry (cjs/index.js) re-exports the upstream pdf-lib API without any credential reads, exfiltration, dropper, or silent-relay behavior, and package.json declares no preinstall/install/postinstall/prepare lifecycle scripts, so installing the package does not auto-execute any code. The dormant SheetJS bundles are not referenced from the main entry. Name-similarity to a top-tier package combined with an irrelevant payload bundle warrants human assessment of intent, but there is no concrete installer-harm mechanism observable in the shipped code.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for pdf-lib-enhanced (version 2.2.0).
If you installed it — respond
pdf-lib-enhanced is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If pdf-lib-enhanced 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks pdf-lib-enhanced-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.