@GSAS/GSAS-SDK · GHSA-px6w-4894-4v4g · Package
UNINSTALL IT, ROTATE THE KEYS IT COULD READ
Not triaged yet. The sources’ own description is below.
first public Aug 24, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Unknown from the sources.
Unknown from the sources.
-= Per source details. Do not edit below this line.=-
@gsas/gsas-sdk@999.9.15 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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
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.