kip-mcp-httpnpm
Advisory published Updated
kip-mcp-http is a confirmed malicious npm package (MAL-2026-11470) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in kip-mcp-http (npm)
What this malware does
lib/report.js imports child_process, fs, https, and os and, via execSync plus fs.readFileSync calls, gathers host identifiers (os.hostname(), os.userInfo()) and file contents, then POSTs the collected data to a hardcoded external endpoint at hooks.zapier.com (https.request on line 118, POST on line 121, URL literal on line 12). The destination is an author-controlled webhook unrelated to any declared MCP/HTTP functionality, and the collection combines system reconnaissance with filesystem reads before transmission.
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
Malicious packageFind it
Search your lockfiles and build artifacts for kip-mcp-http (version 1.0.0).
If you installed it — respond
Remove kip-mcp-http from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If kip-mcp-http 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 kip-mcp-http-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.