sap-mcp-confignpm
sap-mcp-config is a confirmed malicious npm package (MAL-2026-11481) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sap-mcp-config (npm)
What this malware does
The package (name suggests an SAP MCP configuration helper) ships lib/report.js which, from a postinstall hook, collects developer identity data — email addresses resolved via gh api user/emails, git config user.email, npm config get email, and the GIT_AUTHOR_EMAIL/EMAIL environment variables — together with os.hostname() and os.userInfo() output, and POSTs the collected data via https.request to a hardcoded webhook at https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. The destination is an author-controlled Zapier endpoint that is unrelated to the package's stated SAP/MCP configuration purpose. The code contains a consent-gate path that, on interactive TTY runs of the CLI, prompts the user before sending and records the answer in ~/.install-email-research.json; however, the collection primitives (execSync of gh/git/npm, env reads, os identity APIs) and the hardcoded exfiltration endpoint are present in the shipped code path, and the postinstall entrypoint re-invokes the reporter. The package self-labels as "security research" by "Capsule Security", a cover-story framing that does not change the behavior: developer email plus host identity are being sent to a third-party webhook controlled by the author.
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 sap-mcp-config (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sap-mcp-config across your stack and pipelines.
If you installed it — respond
sap-mcp-config 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 sap-mcp-config 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 sap-mcp-config 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 sap-mcp-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.