@gsas/gsas-sdk
This report shows the evidence for @gsas/gsas-sdk@999.9.15, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-14420 confirms this npm version as malicious.
Advisory
MAL-2026-14420
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @gsas/gsas-sdk (npm)
Details
@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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @gsas/gsas-sdk@999.9.15.
The versions list below shows the verdict for each recorded version.
- Avoid installing @gsas/gsas-sdk@999.9.15. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.