MAL-2026-6456 Malicious code in stitch-design (npm)
Malicious package
Published
MAL-2026-6456 is a malicious package: stitch-design (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-6456/ (Markdown: https://insights.sbomify.com/MAL-2026-6456/index.md)
- Package
- stitch-design
- Registry
- npm
What is MAL-2026-6456?
MAL-2026-6456 is a malicious package in stitch-design, published on 25 Jun 2026.
Official description
The npm package ships a preinstall lifecycle hook (scripts/preinstall.js) that, on
npm install, reads classic installer-secret paths — ~/.gitconfig, ~/.git-credentials, ~/.ssh/*.pub, ~/.npmrc, ~/.docker/config.json — and runs subprocesses (git config --global/--system user.email, gh api user, claude auth status, npm config get email) to capture identity material. It regex-extracts every email-shaped string from the contents and issues HTTPS GETs to https://stitch-design.ai/api/v1?src=...&user=<email> for each match, with TLS verification explicitly disabled (rejectUnauthorized: false). The same harvester is duplicated in bin/cli.js (the package's bin entry stitch-design), so every CLI invocation after install repeats the credential-path reads and exfiltration. Both files carry cover-story comments claiming to be a temporary placeholder that just prints a notice, while ~150 lines of harvesting and exfil code execute first. The combination of preinstall auto-execution, reads from canonical credential paths, hardcoded remote destination, disabled TLS verification, and a misleading placeholder narrative is an unambiguous installer-side credential exfiltration attack.What should I do about MAL-2026-6456?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.