@galicia-toolkit-nestjs/swagger

@galicia-toolkit-nestjs/swagger is a dependency confusion package published to npm on 2026-10-09 by the account s4yhii__, targeting the internal @galicia-toolkit-* / @brick-v2 package namespaces with inflated versions (e.g. 999.0.x). Early versions resolve <hostname>.<tag>.dc.oob.s4yhii.com via DNS to beacon the victim's hostname. Later versions run `node index.js` from a preinstall hook, which loads a bundled native addon (prebuilds/<platform>-<arch>/metrics.node, Linux and Windows builds). The addon forks a detached process that collects hostname, username, OS/arch, cwd and the full values of CI/cloud secrets from environment variables (NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, SYSTEM_ACCESSTOKEN, AZURE_DEVOPS_EXT_PAT and others) and sends them as JSON via HTTP POST /native to oob.s4yhii.com:9999.

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (605d8d8afe172d78840f3617c35733b47635a3482beba461bc1015c45840e250)
The package presents itself as a NestJS Swagger integration (name resembles @nestjs/swagger, published at version 999.0.2 in a dependency-confusion shape) but ships a stub JavaScript API (forRoot/createLogger returning empty) that, on require(), loads a prebuilt native addon at prebuilds/<platform>-<arch>/metrics.node inside a try/catch that silently swallows errors. The native binary reads credential-grade environment variables including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, and ACTIONS_ID_TOKEN_REQUEST_TOKEN, collects host identity (hostname, uid via getpwuid/getuid, cwd, uname/release, arch, and the package tag passed in via _METRICS_PKG), formats a JSON payload, and sends it over a raw socket (gethostbyname+connect+send, HTTP/1.0 POST /native) to the hardcoded host oob.s4yhii.com. The loader daemonizes via fork+setsid to persist beyond the parent process. On any npm install followed by import/require of this package in a build pipeline, cloud credentials, GitHub Actions OIDC tokens, and npm publish tokens leave the host to an attacker-controlled endpoint.