@medisend/webview-bridge@0.0.1-security-research

package.json declares a postinstall lifecycle script that runs curl to https://webhook.site/74ed1be3-96d6-48c3-932b-6b1dbabaff97 with query parameters populated from $(whoami), $(hostname), $(pwd), $(ls -la), and $(node -v). On every npm install the installer's username, hostname, working directory, a directory listing of the install location, and Node.js version are sent to a third-party webhook.site collector controlled by whoever provisioned that endpoint. The package publishes under the @medisend scope and its description states a dependency-confusion test referencing a third-party VDP; an installer whose internal tooling resolves the public registry version instead of an internal @medisend package will trigger this exfiltration automatically. ## Source: ghsa-malware (0480ab32758999df6fe5905502ce7b3cbf0ef1c2377cf006facaa2a47a68d26f) 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. ## Source: ossf-package-analysis (bcefced9c742cce25a3c42fdb4cd5c9f2545184e7b661fff98f362ba0a566ce1) The OpenSSF Package Analysis project identified '@medisend/webview-bridge' @ 0.0.2-security-research (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.