@brick-v2/brand@999.0.3
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-17714 confirms this npm version as malicious.
Advisory
MAL-2026-17714
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @brick-v2/brand (npm)
Details
package.json declares a preinstall hook `node index.js || true` that loads a prebuilt native addon at prebuilds/<platform>-<arch>/metrics.node. The addon reads credential-grade environment variables (AWS_SECRET_ACCESS_KEY and other AWS_*, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, AZURE_DEVOPS_EXT_PAT) and host identifiers (hostname via gethostname/GetComputerNameA, username via getpwuid/GetUserNameA, uname release, cwd, package name), serializes them into a JSON payload of shape `{"src":"native","pkg":...,"h":...,"u":...,"os":...,"arch":...,"rel":...,"cwd":...,"e":{...}}`, and transmits it via a raw TCP socket (socket/connect/send, with setsid+fork daemonization on Linux) to the hardcoded host oob.s4yhii.com using `POST /native HTTP/1.0`. The same exfiltration behavior is present in both the linux-x64 and win32-x64 prebuilt binaries. The JavaScript entry point exports only inert NestJS-style `forRoot` / `createLogger` placeholders; the entire operational behavior resides in the opaque native binary. The package is published under the private-looking scope `@brick-v2` at version `999.0.3`, a version-inflation shape consistent with dependency-confusion resolution against an internal `@brick-v2` scope.
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/brand@999.0.3.
The same advisory and Firewall decision cover 2 recorded versions
999.0.1, 999.0.3
See all versions of @brick-v2/brand for other recorded verdicts.
- Avoid installing @brick-v2/brand@999.0.3. 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.