supply chain event / NVI-00009749 / Revision 1
Malicious code in @brick-v2/tour (npm)
GitHub lists this malware advisory for @brick-v2/tour, @brick-v2/tour, @brick-v2/tour, @brick-v2/tour. 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.
@brick-v2/tour
source listed= 999.0.1
## Source: amazon-inspector (aabec40c085d56f59b4ca696eefe600f450a03284df0d77f562d861fed091bee) The package presents itself as an Angular-style module exposing forRoot/createLogger stubs and a version field, but these exports are no-ops. The real behavior is in a bundled prebuilt native addon at prebuilds/linux-x64/metrics.node and prebuilds/win32-x64/metrics.node. package.json declares `"preinstall": "node index.js || true"`, and index.js loads the platform-specific metrics.node via `require(path.join(__dirname,'prebuilds', os.platform()+'-'+os.arch(),'metrics.node'))`, so the native addon is executed automatically on `npm install` and again on `require()`. The native binary reads a broad set of credential-grade environment variables and host identifiers — AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, SYSTEM_ACCESSTOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, AZURE_DEVOPS_EXT_PAT, plus hostname, username, cwd, OS and arch — and POSTs them as JSON (template `{"src":"native","pkg":"%s",...}`) to `oob.s4yhii.com` at path `/native` over HTTP/1.0. The `|| true` in the preinstall hook suppresses errors so the instal
@brick-v2/tour
source listed= 999.0.3
## Source: amazon-inspector (aabec40c085d56f59b4ca696eefe600f450a03284df0d77f562d861fed091bee) The package presents itself as an Angular-style module exposing forRoot/createLogger stubs and a version field, but these exports are no-ops. The real behavior is in a bundled prebuilt native addon at prebuilds/linux-x64/metrics.node and prebuilds/win32-x64/metrics.node. package.json declares `"preinstall": "node index.js || true"`, and index.js loads the platform-specific metrics.node via `require(path.join(__dirname,'prebuilds', os.platform()+'-'+os.arch(),'metrics.node'))`, so the native addon is executed automatically on `npm install` and again on `require()`. The native binary reads a broad set of credential-grade environment variables and host identifiers — AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, SYSTEM_ACCESSTOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, AZURE_DEVOPS_EXT_PAT, plus hostname, username, cwd, OS and arch — and POSTs them as JSON (template `{"src":"native","pkg":"%s",...}`) to `oob.s4yhii.com` at path `/native` over HTTP/1.0. The `|| true` in the preinstall hook suppresses errors so the instal
@brick-v2/tour
source listed= 999.0.2
## Source: amazon-inspector (aabec40c085d56f59b4ca696eefe600f450a03284df0d77f562d861fed091bee) The package presents itself as an Angular-style module exposing forRoot/createLogger stubs and a version field, but these exports are no-ops. The real behavior is in a bundled prebuilt native addon at prebuilds/linux-x64/metrics.node and prebuilds/win32-x64/metrics.node. package.json declares `"preinstall": "node index.js || true"`, and index.js loads the platform-specific metrics.node via `require(path.join(__dirname,'prebuilds', os.platform()+'-'+os.arch(),'metrics.node'))`, so the native addon is executed automatically on `npm install` and again on `require()`. The native binary reads a broad set of credential-grade environment variables and host identifiers — AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, SYSTEM_ACCESSTOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, AZURE_DEVOPS_EXT_PAT, plus hostname, username, cwd, OS and arch — and POSTs them as JSON (template `{"src":"native","pkg":"%s",...}`) to `oob.s4yhii.com` at path `/native` over HTTP/1.0. The `|| true` in the preinstall hook suppresses errors so the instal
@brick-v2/tour
source listed> 0
## Source: amazon-inspector (aabec40c085d56f59b4ca696eefe600f450a03284df0d77f562d861fed091bee) The package presents itself as an Angular-style module exposing forRoot/createLogger stubs and a version field, but these exports are no-ops. The real behavior is in a bundled prebuilt native addon at prebuilds/linux-x64/metrics.node and prebuilds/win32-x64/metrics.node. package.json declares `"preinstall": "node index.js || true"`, and index.js loads the platform-specific metrics.node via `require(path.join(__dirname,'prebuilds', os.platform()+'-'+os.arch(),'metrics.node'))`, so the native addon is executed automatically on `npm install` and again on `require()`. The native binary reads a broad set of credential-grade environment variables and host identifiers — AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, SYSTEM_ACCESSTOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, AZURE_DEVOPS_EXT_PAT, plus hostname, username, cwd, OS and arch — and POSTs them as JSON (template `{"src":"native","pkg":"%s",...}`) to `oob.s4yhii.com` at path `/native` over HTTP/1.0. The `|| true` in the preinstall hook suppresses errors so the instal
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-4w7c-9xc7-gwv7 ↗
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.