MAL-2026-6263 Malicious code in gd-auth-client (npm)
Malicious package
Published
MAL-2026-6263 is a malicious package: gd-auth-client (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-6263/ (Markdown: https://insights.sbomify.com/MAL-2026-6263/index.md)
- Package
- gd-auth-client
- Registry
- npm
What is MAL-2026-6263?
MAL-2026-6263 is a malicious package in gd-auth-client, published on 22 Jun 2026.
Official description
package.json declares
preinstall: node index.js, which runs automatically on npm install. index.js requires os, dns, https, querystring, and the local package.json, then collects installer host identifiers — homedir (os.homedir()), hostname (os.hostname()), username (os.userInfo().username), configured DNS servers (dns.getServers()), current working directory (__dirname), and the full package.json contents — and POSTs them via HTTPS to 6pwzxcku93yjz1m1mp1ctzofj6pxdn1c.oastify.com/dependency-confusion, a Burp Collaborator (OAST) subdomain controlled by the publisher. The version number 999.0.0 combined with a generic, unscoped name is the standard dependency-confusion shape: the package is published to the public registry to win resolution against an internal/private package of the same name in a victim's build, at which point the preinstall hook beacons home with environment fingerprints suitable for follow-up targeting. Any developer or CI system that resolves this package suffers immediate exfiltration of host identity to an attacker-controlled endpoint at install time.What should I do about MAL-2026-6263?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.