Which versions of relativity-pdfjs-dist are malicious?

The following npm versions of relativity-pdfjs-dist are flagged malicious: 5.8.2, 99.9.9. Treat any of these as compromised.

How do I remediate relativity-pdfjs-dist if I installed it?

relativity-pdfjs-dist is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed relativity-pdfjs-dist — how do I know if it already compromised me?

If relativity-pdfjs-dist 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 relativity-pdfjs-dist part of a known attack campaign?

Yes — relativity-pdfjs-dist is associated with the IN-MAL-2026-011142, IN-MAL-2026-011143 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 relativity-pdfjs-dist 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 relativity-pdfjs-dist (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging relativity-pdfjs-dist across your stack and pipelines.

Malicious package

relativity-pdfjs-distnpm

relativity-pdfjs-dist is a confirmed malicious npm package (MAL-2026-10778) that steals credentials and exfiltrates sensitive data (malicious versions 5.8.2, 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in relativity-pdfjs-dist (npm)

MAL-2026-10778

Immediate action

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

npm uninstall relativity-pdfjs-dist

What this malware does

package.json declares a preinstall script that runs node -e inline JavaScript on npm install. The inline code collects the installer's hostname, username, current working directory, npm registry configuration, CI environment markers (CI, GITHUB_REPOSITORY, JENKINS_URL), and platform, base64-encodes the JSON, and sends it as an HTTPS GET query parameter to 9u4hlcu3febavvzbrqulpuwf66cy0qof.oastify.com, a Burp Collaborator out-of-band exfiltration endpoint. The package name resembles the legitimate pdfjs-dist package and the version number 99.9.9 is a dependency-confusion pattern intended to outrank an internal package of the same name.

The OpenSSF Package Analysis project identified 'relativity-pdfjs-dist' @ 5.8.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

5.8.299.9.9

Indicators of compromise (SHA-256)

c48b9caf30af59020f36b25fb13fb54db5754b9d8ad311f857843171cc88915a

8a40319295154d72e1485a810cfd456ee7d44cabe572cba35912723f838edb65

542f0656a76929fa6bd11c9d8ff36f9f69c5865f46d835b8c707a803d71aa55f

74184da64255136795ef84ac6057c0889494a68689a5aec9832c7e8d08dac8d9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for relativity-pdfjs-dist (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging relativity-pdfjs-dist across your stack and pipelines.
If you installed it — respond
relativity-pdfjs-dist is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If relativity-pdfjs-dist 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 relativity-pdfjs-dist 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. relativity-pdfjs-dist on npm has been identified as a malicious package (versions 5.8.2, 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011142IN-MAL-2026-011143

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks relativity-pdfjs-dist-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database