Malicious code in @medisend/core (npm)
The npm package @medisend/core version 0.0.1-security-research contains malicious code in its postinstall script that sends the installer's hostname to a third-party URL without consent. This package is designed to exploit dependency confusion in internal builds expecting a private package, causing unintended data leakage and potential system compromise. Removal of the package may not fully remediate the compromise, and all secrets on affected systems should be rotated.
AI Analysis
Technical Summary
The @medisend/core npm package version 0.0.1-security-research declares a postinstall lifecycle script that executes a curl command to transmit the installer's hostname to a webhook.site URL controlled by an attacker. This behavior leaks host identifiers off-host during installation. The package targets internal builds expecting a private @medisend/core package, exploiting dependency confusion to run this malicious code automatically. According to the GHSA-malware source, any system with this package installed or running should be considered fully compromised, with potential full control given to an external entity. Secrets and keys on affected systems must be rotated, and removal of the package alone may not remove all malicious artifacts.
Potential Impact
Installation of this package results in unauthorized exfiltration of the installer's hostname to an attacker-controlled endpoint. The package's postinstall script executes automatically, potentially leading to full system compromise. Attackers may gain control over the affected system, risking exposure of all stored secrets and keys. The compromise is severe enough that affected systems should be treated as fully compromised, requiring secret rotation and thorough remediation beyond package removal.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove the @medisend/core package version 0.0.1-security-research from any affected systems. Treat any system with this package installed as fully compromised and rotate all secrets and keys from a separate, trusted system. Monitor for any signs of persistent compromise and consider full system remediation. Avoid installing packages from untrusted or unexpected sources, especially those mimicking private packages to prevent dependency confusion attacks.
Malicious code in @medisend/core (npm)
Description
The npm package @medisend/core version 0.0.1-security-research contains malicious code in its postinstall script that sends the installer's hostname to a third-party URL without consent. This package is designed to exploit dependency confusion in internal builds expecting a private package, causing unintended data leakage and potential system compromise. Removal of the package may not fully remediate the compromise, and all secrets on affected systems should be rotated.
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 @medisend/core npm package version 0.0.1-security-research declares a postinstall lifecycle script that executes a curl command to transmit the installer's hostname to a webhook.site URL controlled by an attacker. This behavior leaks host identifiers off-host during installation. The package targets internal builds expecting a private @medisend/core package, exploiting dependency confusion to run this malicious code automatically. According to the GHSA-malware source, any system with this package installed or running should be considered fully compromised, with potential full control given to an external entity. Secrets and keys on affected systems must be rotated, and removal of the package alone may not remove all malicious artifacts.
Potential Impact
Installation of this package results in unauthorized exfiltration of the installer's hostname to an attacker-controlled endpoint. The package's postinstall script executes automatically, potentially leading to full system compromise. Attackers may gain control over the affected system, risking exposure of all stored secrets and keys. The compromise is severe enough that affected systems should be treated as fully compromised, requiring secret rotation and thorough remediation beyond package removal.
Defensive Guidance
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove the @medisend/core package version 0.0.1-security-research from any affected systems. Treat any system with this package installed as fully compromised and rotate all secrets and keys from a separate, trusted system. Monitor for any signs of persistent compromise and consider full system remediation. Avoid installing packages from untrusted or unexpected sources, especially those mimicking private packages to prevent dependency confusion attacks.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14422
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-wfxf-4cwg-r55p"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a9f9111acd9273b49ff2afc
Added to database: 09/08/2026, 04:37:37 UTC
Last enriched: 09/08/2026, 05:09:34 UTC
Last updated: 09/08/2026, 19:36:14 UTC
Views: 10
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.