Which versions of pdf-linker are malicious?

Every published version of pdf-linker on npm is considered malicious. Remove the package entirely.

How do I remediate pdf-linker if I installed it?

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

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

Yes — pdf-linker is associated with the GHSA-mwqh-c7j6-f7p2 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-linker across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pdf-linker (all published versions).

Malicious package

pdf-linkernpm

Advisory published Apr 15, 2026Updated Apr 23, 2026

pdf-linker is a confirmed malicious npm package (MAL-2026-2677) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pdf-linker (npm)

MAL-2026-2677

Immediate action

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

npm uninstall pdf-linker

What this malware does

The package pdf-linker was found to contain malicious 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

b496570e3a5a77b10f653cddc3b93d0ae974b01b253f0468a02c169c9fc0eb2c

14402ea1542260a2cb6471902d5e0d037fecb136e1f2b2995b2741eb775f495d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pdf-linker (all published versions).
If you installed it — respond
Remove pdf-linker 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 pdf-linker 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. pdf-linker on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mwqh-c7j6-f7p2

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pdf-linker-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