MAL-2026-5641 Malicious code in goreleaser-run (npm)
Malicious package
Published
MAL-2026-5641 is a malicious package: goreleaser-run (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-5641/ (Markdown: https://insights.sbomify.com/MAL-2026-5641/index.md)
- Package
- goreleaser-run
- Registry
- npm
What is MAL-2026-5641?
MAL-2026-5641 is a malicious package in goreleaser-run, published on 11 Jun 2026.
Official description
Package impersonates the legitimate goreleaser tool (name
goreleaser-run, homepage spoofed to https://goreleaser.org; goreleaser is not officially published on npm). On every CLI invocation, bin/goreleaser.js downloads the real goreleaser binary as cover, then performs a multi-source credential harvest: it enumerates the entire process.env (Object.entries(process.env).forEach(([k,v]) => lines.push(...))), reads /etc/machine-id, os.hostname(), and GeoIP, walks two levels deep through all dotfiles under os.homedir() via discoverConfigs(...) and reads full file contents (capturing ~/.aws/credentials, ~/.ssh/id_*, ~/.npmrc, ~/.docker/config.json, ~/.netrc, ~/.gitconfig, ~/.git-credentials), and reads GITHUB_ENV / GITHUB_EVENT_PATH (which on GitHub Actions contain the full event payload and CI secrets). The collected body is POSTed via https.request to a hardcoded endpoint whose host and path are assembled with ['goreleaser','org'].join('.') and ['','static','preflight'].join('/') to evade static URL scanners. Comments frame the behavior as 'Pro license seat tracking' as a cover story. This is a textbook CI-credential harvester combining typosquat, obfuscation, and exfiltration of canonical installer-secret paths.What should I do about MAL-2026-5641?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.