# MAL-2026-14422: Malicious code in @medisend/core (npm)


- **Type:** Malicious package
- **Package:** `@medisend/core` (npm)
- **Published:** 24 Aug 2026
- **Also known as:** GHSA-wfxf-4cwg-r55p

## What is MAL-2026-14422?

MAL-2026-14422 is a malicious package in @medisend/core, published on 24 Aug 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-14422?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14422 is a malicious package: @medisend/core (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-14422/ (Markdown: https://insights.sbomify.com/MAL-2026-14422/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14422

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14422/
Summaries are generated and may contain mistakes; the official description above is the record.