Which versions of ryan-pdf-js are malicious?

The following npm versions of ryan-pdf-js are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate ryan-pdf-js if I installed it?

ryan-pdf-js is a typosquat — you almost certainly intended a legitimately-named package. Remove ryan-pdf-js, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed ryan-pdf-js — how do I know if it already compromised me?

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

Yes — ryan-pdf-js is associated with the IN-MAL-2026-007677 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 ryan-pdf-js 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 ryan-pdf-js (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ryan-pdf-js across your stack and pipelines.

Malicious package

ryan-pdf-jsnpm

Malicious code in ryan-pdf-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6546

Immediate action

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

npm uninstall ryan-pdf-js

What this malware does

[email protected] 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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

c3d966501b5f533318c26b54887cd29b3cd6c9495035a0f74519ba349357e3eb

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ryan-pdf-js (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ryan-pdf-js across your stack and pipelines.
If you installed it — respond
ryan-pdf-js is a typosquat — you almost certainly intended a legitimately-named package. Remove ryan-pdf-js, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If ryan-pdf-js 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 ryan-pdf-js 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. ryan-pdf-js 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-007677

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ryan-pdf-js-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