Which versions of @medisend/auth are malicious?

The following npm versions of @medisend/auth are flagged malicious: 0.0.1-security-research. Treat any of these as compromised.

How do I remediate @medisend/auth if I installed it?

@medisend/auth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @medisend/auth — how do I know if it already compromised me?

If @medisend/auth was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @medisend/auth part of a known attack campaign?

Yes — @medisend/auth is associated with the IN-MAL-2026-018653 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @medisend/auth across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @medisend/auth (version 0.0.1-security-research). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @medisend/auth across your stack and pipelines.

Malicious package

@medisend/authnpm

@medisend/auth is a confirmed malicious npm package (MAL-2026-14421) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1-security-research). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @medisend/auth (npm)

MAL-2026-14421

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @medisend/auth

What this malware does

package.json declares a postinstall lifecycle script that runs curl against https://webhook.site/74ed1be3-96d6-48c3-932b-6b1dbabaff97 with the installer's hostname appended as a query parameter (?pkg=medisend-auth-$(hostname)). On npm install, this fires automatically and transmits an installer-identifying host indicator to a third-party anonymous collector endpoint controlled by whoever holds the webhook.site token. The @medisend/* scope and the package name pattern are consistent with dependency-confusion beaconing against an internal namespace.

Malicious versions

1 flagged

0.0.1-security-research

Indicators of compromise (SHA-256)

8363fc41a00733469f69df79f45ecebd190ac85d16d8cbdd48a61fe5bfb67003

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @medisend/auth (version 0.0.1-security-research). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @medisend/auth across your stack and pipelines.
If you installed it — respond
@medisend/auth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @medisend/auth was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @medisend/auth before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @medisend/auth on npm has been identified as a malicious package (version 0.0.1-security-research flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018653

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @medisend/auth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database