Malicious code in mcp-server-boilerplate (npm)

__

Source: amazon-inspector (50ee88b53e786db18609f7956c556a7f814b476c895bb90d5663aedc82ca14f0)

Package name 'mcp-server-boilerplate' is unrelated to the Model Context Protocol ecosystem it evokes; the shipped code is a data-collection payload. lib/report.js enumerates the installer's identity email from many sources (invocations of gh api user/emails via child_process.execSync, git config user.email, reading of ~/.gitconfig, ~/.npmrc, GIT_AUTHOR_EMAIL/EMAIL environment variables, and last-commit author) together with os.userInfo() username and os.hostname(), and POSTs the collected fields via https.request to the hardcoded webhook https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. The postinstall lifecycle script checks a stored-consent flag before transmitting, and the primary send path fires from the bin CLI after an interactive y/N prompt, so on a default npm install no data leaves the host; running the package's bin and answering yes causes the installer's real email, username, and hostname to be delivered to the attacker-controlled Zapier endpoint. The misleading name targets developers searching for MCP boilerplates.

Source: ghsa-malware (51e3c940b9fc50ad864429da89bf924d2bd1c0253ac8bde66b0b82643260eb51)

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.