MAL-2026-14420 Malicious code in @gsas/gsas-sdk (npm)
Malicious package
Published
MAL-2026-14420 is a malicious package: @gsas/gsas-sdk (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-14420/ (Markdown: https://insights.sbomify.com/MAL-2026-14420/index.md)
- Package
- @gsas/gsas-sdk
- Registry
- npm
What is MAL-2026-14420?
MAL-2026-14420 is a malicious package in @gsas/gsas-sdk, published on 24 Aug 2026.
Official description
@gsas/[email protected] is a high-version public-registry squat targeting an internal
@gsas/gsas-sdk name. package.json declares preinstall: node index.js, and index.js runs on install to collect the installer's hostname, username, home directory, cwd, local/public/resolver IPs, npm registry URL, CI platform with repo/actor/run/workflow/runner, AWS region, git email domain, and the consuming project's name/author/repo/homepage. It also spawns gh api user --jq.login, npm whoami, and git config user.email to capture the developer's authenticated GitHub login, npm login, and email. The collected JSON is hex-encoded, split into 60-character chunks emitted as DNS subdomain queries under da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun, and additionally POSTed over HTTP and HTTPS to the same host (path /poc/<uuid>). Public-IP discovery calls out to api.ipify.org, icanhazip.com, and ifconfig.me. Comments in the file describe the multi-channel design as intended to survive corporate egress filtering. An AUTHORISED SECURITY RESEARCH self-label appears in the source but does not correspond to installer consent.What should I do about MAL-2026-14420?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.