@medisend/sharednpm
Advisory published Updated
@medisend/shared is a confirmed malicious npm package (MAL-2026-14423) that opens a backdoor for remote access (malicious version 0.0.1-security-research). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @medisend/shared (npm)
What this malware does
package.json declares a postinstall lifecycle script that runs curl at install time and transmits the installer's hostname (via $(hostname)) as a query parameter to a webhook.site collector. The receiver ID in the URL is left as a <your-id> placeholder, so the beacon URL is not fully configured, but the postinstall hook still fires on npm install and issues an outbound request carrying host identification to a third-party collector. The package version tag also self-labels as security-research, but the shipped behavior — an automatic install-time beacon of host identity to an external collector — matches dependency-confusion / reconnaissance beacon shape rather than a benign library.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for @medisend/shared (version 0.0.1-security-research).
If you installed it — respond
@medisend/shared establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @medisend/shared was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @medisend/shared-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.