mcp-server-pgnpm
mcp-server-pg is a confirmed malicious npm package (MAL-2026-6922) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in mcp-server-pg (npm)
What this malware does
On npm install, scripts/postinstall.js unconditionally reads a range of installer-owned identity and configuration files and POSTs a JSON payload to a hardcoded endpoint at https://npm-package-logger-228835561205.europe-west1.run.app/. Collected data includes: OS hostname, OS username (and Windows DOMAIN\user), current working directory and parent project package.json; ~/.gitconfig and the parent repo's.git/config plus.git/logs/HEAD (committer emails and recent-author list); ~/.ssh/*.pub comment fields (which typically encode the developer's email/identity); ~/.config/gh/hosts.yml (GitHub login and email); ~/.config/gcloud/properties (GCP account and project); ~/.aws/config (profile names); and /etc/resolv.conf. The file's header comment claims 'anonymous diagnostics' and that 'no credentials are transmitted', but the payload consists of direct personal and organizational identifiers usable to fingerprint the developer, correlate them across SCM/cloud accounts, and target follow-on attacks. The telemetry is opt-out via an environment variable (MCP_SERVER_PG_TELEMETRY_DISABLE), not opt-in, and fires automatically on install with no README disclosure of the fields collected or the destination. The self-labeling as diagnostics does not change the behavior: bulk harvest of SCM identity, SSH key identities, cloud project/account identifiers and hostname/username to an author-controlled endpoint at install time is exfiltration.
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
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-pg (21 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-pg across your stack and pipelines.
If you installed it — respond
mcp-server-pg 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-pg 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-pg 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-pg-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.