supply chain event / NVI-00009657 / Revision 1
Malicious code in @brick-v2/core (npm)
GitHub lists this malware advisory for @brick-v2/core, @brick-v2/core, @brick-v2/core. 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/core
source listed= 999.0.2
## Source: amazon-inspector (90c1fd9505ce4256620f9cb647e3a57a5af52539aa1e717a3eecb0485dec8c83) The package's main entry `index.js` loads a prebuilt native binary at `prebuilds/-/metrics.node` inside a top-level try/catch, executing native code within the Node process as soon as the module is required. The ELF binary reads credential-grade environment variables including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, and ACTIONS_ID_TOKEN_REQUEST_TOKEN, along with hostname, uid, and current working directory, and POSTs them as JSON to the hardcoded host `oob.s4yhii.com` via a raw socket (`POST /native HTTP/1.0`). The native code also invokes `fork`/`setsid` to detach from the parent process. The package is published as `@brick-v2/core` at version `999.0.1` with a trivial JS wrapper, a generic `core module` description, and `UNLICENSED` — a shape consistent with a dependency-confusion payload targeting a private `@brick-v2` scope so that npm resolution prefers this public version over an internal package. --- Credit: OpenSSF
@brick-v2/core
source listed= 999.0.1
## Source: amazon-inspector (90c1fd9505ce4256620f9cb647e3a57a5af52539aa1e717a3eecb0485dec8c83) The package's main entry `index.js` loads a prebuilt native binary at `prebuilds/-/metrics.node` inside a top-level try/catch, executing native code within the Node process as soon as the module is required. The ELF binary reads credential-grade environment variables including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, and ACTIONS_ID_TOKEN_REQUEST_TOKEN, along with hostname, uid, and current working directory, and POSTs them as JSON to the hardcoded host `oob.s4yhii.com` via a raw socket (`POST /native HTTP/1.0`). The native code also invokes `fork`/`setsid` to detach from the parent process. The package is published as `@brick-v2/core` at version `999.0.1` with a trivial JS wrapper, a generic `core module` description, and `UNLICENSED` — a shape consistent with a dependency-confusion payload targeting a private `@brick-v2` scope so that npm resolution prefers this public version over an internal package. --- Credit: OpenSSF
@brick-v2/core
source listed> 0
## Source: amazon-inspector (90c1fd9505ce4256620f9cb647e3a57a5af52539aa1e717a3eecb0485dec8c83) The package's main entry `index.js` loads a prebuilt native binary at `prebuilds/-/metrics.node` inside a top-level try/catch, executing native code within the Node process as soon as the module is required. The ELF binary reads credential-grade environment variables including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, and ACTIONS_ID_TOKEN_REQUEST_TOKEN, along with hostname, uid, and current working directory, and POSTs them as JSON to the hardcoded host `oob.s4yhii.com` via a raw socket (`POST /native HTTP/1.0`). The native code also invokes `fork`/`setsid` to detach from the parent process. The package is published as `@brick-v2/core` at version `999.0.1` with a trivial JS wrapper, a generic `core module` description, and `UNLICENSED` — a shape consistent with a dependency-confusion payload targeting a private `@brick-v2` scope so that npm resolution prefers this public version over an internal package. --- Credit: OpenSSF
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-49xp-7x68-8hf4 ↗
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.