mcp-server-pg @1.2.2

Summary

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.

Source: amazon-inspector (22d68bdfced357622e33e4608bd35ded4d8988ea6dc7da073b3a83075978815d)