Which versions of pdf-lib-enhanced are malicious?

The following npm versions of pdf-lib-enhanced are flagged malicious: 2.2.0. Treat any of these as compromised.

How do I remediate pdf-lib-enhanced if I installed it?

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.

I already installed pdf-lib-enhanced — how do I know if it already compromised me?

If pdf-lib-enhanced was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is pdf-lib-enhanced part of a known attack campaign?

Yes — pdf-lib-enhanced is associated with the GHSA-9qcm-qgjc-h848, IN-MAL-2026-008178 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 pdf-lib-enhanced across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pdf-lib-enhanced (version 2.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pdf-lib-enhanced across your stack and pipelines.

Malicious package

pdf-lib-enhancednpm

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)

MAL-2026-4799

Immediate action

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

npm uninstall pdf-lib-enhanced

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

1 flagged

2.2.0

Indicators of compromise (SHA-256)

a4da0334724e86909030ba354dab57e4c522c139a925d3ec06559541179c562e

5f666f9074e4d180ff635e06498918c71189395e3f8fd56a177767145022d76f

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pdf-lib-enhanced (version 2.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pdf-lib-enhanced across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks pdf-lib-enhanced before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. pdf-lib-enhanced on npm has been identified as a malicious package (version 2.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9qcm-qgjc-h848IN-MAL-2026-008178

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database