@medisend/core

Details

**Severity:** Critical

**Affected versions:** `= 0.0.1-security-research`

## Source: amazon-inspector (18f32429d1bfdc9438f2f03f531e5c2fef53e0e69104e3124499cf6f42ce52a1)
package.json declares a postinstall lifecycle script that runs curl against https://webhook.site/<id> with the installer's hostname appended as a query parameter, transmitting the host identifier to a third-party request-inspection collector on every npm install. The package name @medisend/core with version 0.0.1-security-research and a description referencing a dependency-confusion test targets internal builds that expect a private @medisend/core package; when such a build resolves this public package instead, the postinstall runs automatically and leaks the installer's hostname off-host. The self-labelled 'security research' framing does not change the effect: any installer that resolves this package executes an unconsented host-identifier beacon to a destination controlled by whoever provisioned the webhook.site URL.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/72e5d8219b286d7332c4ad2364b87986138cf34c/osv/malicious/npm/@medisend/core/MAL-2026-14422.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/72e5d8219b286d7332c4ad2364b87986138cf34c/osv/malicious/npm/@medisend/core/MAL-2026-14422.json
- https://www.npmjs.com/package/@medisend/core/v/0.0.1-security-research
- https://github.com/advisories/GHSA-gm8x-m9c3-pvhq

Compromised versions (1)

• = 0.0.1-security-research

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.