Malicious code in patientdocuments (npm)
The patientdocuments npm package version 75.0.0 contains malicious code that executes a preinstall script during npm install. This script sends the installer's OS username, current working directory, and hostname to an attacker-controlled endpoint over unencrypted HTTP. The package does not provide any legitimate functionality and is designed solely for reconnaissance and identity exfiltration. The package sets unsafe-perm, allowing the script to run with elevated privileges, increasing the risk of system compromise. Removal of the package does not guarantee full remediation as the system may already be fully compromised.
AI Analysis
Technical Summary
The patientdocuments npm package version 75.0.0 includes a preinstall lifecycle script that runs a wget command to send sensitive environment information (username, working directory, hostname) to a malicious Cloudflare Workers endpoint over plain HTTP. This script also appears in the test and preupdate lifecycle scripts. The package contains no legitimate library code and is a dependency-confusion style malicious package designed for reconnaissance and identity exfiltration. The unsafe-perm flag is set, which can cause the script to execute with root privileges in privileged install contexts. According to the GHSA advisory, any system with this package installed should be considered fully compromised, requiring immediate secret and key rotation and removal of the package.
Potential Impact
The malicious package leaks sensitive system information including the OS username, current working directory, and hostname to an attacker-controlled server. Because unsafe-perm is enabled, the malicious script can execute with root privileges in privileged install contexts, potentially allowing full system compromise. The presence of this package indicates a high likelihood that the system is compromised, and all secrets and keys stored on the system should be considered exposed and rotated immediately. Removing the package alone may not fully remediate the compromise.
Mitigation Recommendations
There is no official patch or fix available for this malicious package. The recommended mitigation is to immediately remove the patientdocuments package version 75.0.0 from all affected systems. Treat any system with this package installed as fully compromised. Rotate all secrets, keys, and credentials from a separate, trusted system. Conduct a thorough security assessment to identify and remediate any additional malicious artifacts or persistence mechanisms that may have been installed. Monitor for any suspicious activity related to this package or its indicators.
Malicious code in patientdocuments (npm)
Description
The patientdocuments npm package version 75.0.0 contains malicious code that executes a preinstall script during npm install. This script sends the installer's OS username, current working directory, and hostname to an attacker-controlled endpoint over unencrypted HTTP. The package does not provide any legitimate functionality and is designed solely for reconnaissance and identity exfiltration. The package sets unsafe-perm, allowing the script to run with elevated privileges, increasing the risk of system compromise. Removal of the package does not guarantee full remediation as the system may already be fully compromised.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The patientdocuments npm package version 75.0.0 includes a preinstall lifecycle script that runs a wget command to send sensitive environment information (username, working directory, hostname) to a malicious Cloudflare Workers endpoint over plain HTTP. This script also appears in the test and preupdate lifecycle scripts. The package contains no legitimate library code and is a dependency-confusion style malicious package designed for reconnaissance and identity exfiltration. The unsafe-perm flag is set, which can cause the script to execute with root privileges in privileged install contexts. According to the GHSA advisory, any system with this package installed should be considered fully compromised, requiring immediate secret and key rotation and removal of the package.
Potential Impact
The malicious package leaks sensitive system information including the OS username, current working directory, and hostname to an attacker-controlled server. Because unsafe-perm is enabled, the malicious script can execute with root privileges in privileged install contexts, potentially allowing full system compromise. The presence of this package indicates a high likelihood that the system is compromised, and all secrets and keys stored on the system should be considered exposed and rotated immediately. Removing the package alone may not fully remediate the compromise.
Mitigation Recommendations
There is no official patch or fix available for this malicious package. The recommended mitigation is to immediately remove the patientdocuments package version 75.0.0 from all affected systems. Treat any system with this package installed as fully compromised. Rotate all secrets, keys, and credentials from a separate, trusted system. Conduct a thorough security assessment to identify and remediate any additional malicious artifacts or persistence mechanisms that may have been installed. Monitor for any suspicious activity related to this package or its indicators.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5752
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-28q9-vg2f-r5m7"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a577eea68715ace43b41289
Added to database: 07/15/2026, 12:36:58 UTC
Last enriched: 07/15/2026, 12:53:44 UTC
Last updated: 07/23/2026, 22:52:48 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.