supply chain event / NVI-00009589 / Revision 1
Malicious code in @galicia-toolkit-nestjs-20/archetype (npm)
GitHub lists this malware advisory for @galicia-toolkit-nestjs-20/archetype, @galicia-toolkit-nestjs-20/archetype, @galicia-toolkit-nestjs-20/archetype. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
@galicia-toolkit-nestjs-20/archetype
source listed= 999.0.2
## Source: amazon-inspector (662603823964bdbc871f386498e949d768c84d99645690ee3b5e904b458536db) On module load, index.js unconditionally require()s a bundled native binary at prebuilds/-/metrics.node inside a try/catch that swallows errors. The ELF reads installer-side credential-grade 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) along with hostname, uid, cwd, and uname, and POSTs a JSON payload to the hardcoded host oob.s4yhii.com via a raw 'POST /native HTTP/1.0' request. The binary calls fork+setsid to detach from the host process. The exfiltration destination is embedded inside the compiled addon rather than exposed in JavaScript, placing it beyond source-level inspection. The declared package scope (NestJS archetype toolkit) has no relationship to the destination host or to native-code execution, and the package ships no C/C++ sources corresponding to the shipped.node binary. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/9a014eb4a
@galicia-toolkit-nestjs-20/archetype
source listed= 999.0.1
## Source: amazon-inspector (662603823964bdbc871f386498e949d768c84d99645690ee3b5e904b458536db) On module load, index.js unconditionally require()s a bundled native binary at prebuilds/-/metrics.node inside a try/catch that swallows errors. The ELF reads installer-side credential-grade 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) along with hostname, uid, cwd, and uname, and POSTs a JSON payload to the hardcoded host oob.s4yhii.com via a raw 'POST /native HTTP/1.0' request. The binary calls fork+setsid to detach from the host process. The exfiltration destination is embedded inside the compiled addon rather than exposed in JavaScript, placing it beyond source-level inspection. The declared package scope (NestJS archetype toolkit) has no relationship to the destination host or to native-code execution, and the package ships no C/C++ sources corresponding to the shipped.node binary. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/9a014eb4a
@galicia-toolkit-nestjs-20/archetype
source listed> 0
## Source: amazon-inspector (662603823964bdbc871f386498e949d768c84d99645690ee3b5e904b458536db) On module load, index.js unconditionally require()s a bundled native binary at prebuilds/-/metrics.node inside a try/catch that swallows errors. The ELF reads installer-side credential-grade 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) along with hostname, uid, cwd, and uname, and POSTs a JSON payload to the hardcoded host oob.s4yhii.com via a raw 'POST /native HTTP/1.0' request. The binary calls fork+setsid to detach from the host process. The exfiltration destination is embedded inside the compiled addon rather than exposed in JavaScript, placing it beyond source-level inspection. The declared package scope (NestJS archetype toolkit) has no relationship to the destination host or to native-code execution, and the package ships no C/C++ sources corresponding to the shipped.node binary. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/9a014eb4a
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-43v2-p79h-pjp9 ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.