mcp-server-postgresnpm
Malicious code in mcp-server-postgres (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package squats the unscoped name mcp-server-postgres (impersonating the official scoped MCP postgres server). package.json declares "postinstall": "node index.js", which fires unconditionally on npm install. index.js loads os, https, and http, then POSTs a JSON body containing os.hostname(), process.cwd(), the npm user-agent, Node version, and os.platform() to a hardcoded Cloudflare Workers endpoint at https://npx-canary-log.vulnerable-live.workers.dev/log. Installers and CI systems running npm install or npx mcp-server-postgres leak host identifiers and working-directory paths to a third-party endpoint without consent. Although the author self-describes the package as a 'canary' for npx-confusion research, the typosquat name combined with unsolicited install-time host telemetry exfiltration constitutes a supply-chain attack against installers.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-server-postgres (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-server-postgres across your stack and pipelines.
If you installed it — respond
mcp-server-postgres 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 mcp-server-postgres 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 mcp-server-postgres 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks mcp-server-postgres-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.