@galicia-toolkit-nestjs/paas@999.0.6
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 14d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17723 confirms this npm version as malicious.
Advisory
MAL-2026-17723
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @galicia-toolkit-nestjs/paas (npm)
Details
The package's main entry (index.js) loads a prebuilt native addon (prebuilds/<platform>-<arch>/metrics.node) inside a try/catch on require. The ELF reads CI and cloud credentials from the environment — 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 — together with host identity and working-directory fields (gethostname, getuid, getpwuid, getcwd, uname) and sends them in a JSON body (fields src, pkg, h, u, os, arch, rel, cwd, e) via a raw socket HTTP POST to oob.s4yhii.com (POST /native HTTP/1.0). The addon imports fork and setsid to daemonize and uses hand-rolled socket/connect/send rather than Node's HTTP API, bypassing Node-level network observability. The package name scope (@galicia-toolkit-nestjs) and implausibly high version (999.0.5) are consistent with a dependency-confusion payload targeting an internal package name. Installing or requiring this package in any environment carrying CI, npm publish, GitHub Actions, or AWS credentials results in those secrets being transmitted to the hardcoded attacker endpoint.
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/paas@999.0.6.
See all versions of @galicia-toolkit-nestjs/paas for other recorded verdicts.
- Avoid installing @galicia-toolkit-nestjs/paas@999.0.6. 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.