Malicious code in paychex-pdftron (npm)
Exact source revision recorded 27 Oct 2026 16:44:03 UTC. It does not establish the source's current position. Latest evidence.
osv · MAL-2026-18289
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d32ec8b2ca67156d94943a27b9b7c98f1888d530d7a6f947e49b40f52ec054b3) [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. ## Source: ghsa-malware (f176a5672301d76d7c08b93a46b074c23cdf0d36d46324d30dc8aceaa55ed707) 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.
- Source published
- 25 Oct 2026 14:42:30 UTC
- Source modified
- 27 Oct 2026 15:45:41 UTC
- Observed here
- 27 Oct 2026 16:44:03 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.