@galicia-toolkit-nestjs-20-lite/paas@1.0.22
OpenSSF/OSV Malicious Advisory
imported 14d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17730 confirms this npm version as malicious.
Advisory
MAL-2026-17730
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @galicia-toolkit-nestjs-20-lite/paas (npm)
Details
The package declares scripts.preinstall `node index.js || true`, and index.js (also the main entry) require()s a platform-specific prebuilt native addon at prebuilds/<platform>-<arch>/metrics.node. The native binary reads a curated list of CI/cloud credential environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, AZURE_DEVOPS_EXT_PAT, and similar), together with hostname, user, OS/arch, and cwd (gethostname/getpwuid/uname/getcwd on Linux; GetUserNameA/GetComputerNameA/GetCurrentDirectoryA on Windows). The collected values are serialized as a JSON body (`{"src":"native","pkg":...,"e":{...}}`) and sent via a raw TCP socket as `POST /native HTTP/1.0` to the hardcoded host oob.s4yhii.com. The exported NestJS surface (forRoot/createLogger) is empty stub code with no real functionality, and a nested manifest at src/archetype/package.json contains the self-identifying marker `s4yhii-poc-2026-10-09` and contact `jesusitpro22@gmail.com`, matching the exfil host. The harmful code path fires automatically on `npm install` via preinstall and again on any require() of the package.
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 @galicia-toolkit-nestjs-20-lite/paas@1.0.22.
The same advisory and Firewall decision cover 2 recorded versions
1.0.22, 1.0.24
See all versions of @galicia-toolkit-nestjs-20-lite/paas for other recorded verdicts.
- Avoid installing @galicia-toolkit-nestjs-20-lite/paas@1.0.22. 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.