# MAL-2026-6546: Malicious code in ryan-pdf-js (npm)


- **Type:** Malicious package
- **Package:** `ryan-pdf-js` (npm)
- **Published:** 27 Jun 2026
- **Also known as:** GHSA-7qr7-hcw4-9826

## What is MAL-2026-6546?

MAL-2026-6546 is a malicious package in ryan-pdf-js, published on 27 Jun 2026. 

### Official description

ryan-pdf-js@99.9.1 is an empty stub package (index.js exports {}) whose sole purpose is to deliver an off-registry payload at install time. Its package.json declares its only dependency, `ltidisafe`, as a direct HTTPS tarball URL on a generic Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.1.1.tgz) rather than a registry name, bypassing npm registry scanning. On `npm install`, npm fetches and unpacks that tarball, and any lifecycle scripts it contains execute on the installer's machine. The bucket path `depenconf/` is consistent with dependency-confusion staging, and the package name evokes the widely-used pdf.js ecosystem while shipping no real implementation — a typosquat-shaped lure whose only effect is to route installs through the off-registry dropper.

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.

## What should I do about MAL-2026-6546?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6546 is a malicious package: ryan-pdf-js (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6546/ (Markdown: https://insights.sbomify.com/MAL-2026-6546/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6546

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6546/
Summaries are generated and may contain mistakes; the official description above is the record.