@brick-v2/core@999.0.1
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-17715 confirms this npm version as malicious.
Advisory
MAL-2026-17715
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @brick-v2/core (npm)
Details
The package's main entry `index.js` loads a prebuilt native binary at `prebuilds/<platform>-<arch>/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.
References
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 @brick-v2/core@999.0.1.
The same advisory and Firewall decision cover 2 recorded versions
999.0.1, 999.0.2
See all versions of @brick-v2/core for other recorded verdicts.
- Avoid installing @brick-v2/core@999.0.1. 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.