Which versions of paychex-pdftron are malicious?

The following npm versions of paychex-pdftron are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate paychex-pdftron if I installed it?

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

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

Yes — paychex-pdftron is associated with the IN-MAL-2026-021684 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 paychex-pdftron across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for paychex-pdftron (version 99.9.1).

Malicious package

paychex-pdftronnpm

Advisory published Oct 25, 2026Updated Oct 25, 2026

paychex-pdftron is a confirmed malicious npm package (MAL-2026-18289) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in paychex-pdftron (npm)

MAL-2026-18289

Immediate action

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

npm uninstall paychex-pdftron

What this malware does

[email protected] ships an empty stub (module.exports = {}) and declares its sole dependency ltidisafe as a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.5.tgz) rather than a registry version range. On npm install, npm fetches whatever bytes that URL returns and installs the resulting package, executing any lifecycle scripts it contains — with no version pin, no integrity hash, and no signature verification. The package name resembles an internal Paychex scope, the version is an implausibly high 99.9.1 (a dependency-confusion resolution tactic), the URL path segment is depenconf, and the host is unrelated to any legitimate Paychex or pdftron domain. The manifest alone is the attack surface: resolving this dependency pulls attacker-controlled code into the installer's build environment.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

d32ec8b2ca67156d94943a27b9b7c98f1888d530d7a6f947e49b40f52ec054b3

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-021684

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks paychex-pdftron-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