@brick-v2/table@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-17718 confirms this npm version as malicious.
Advisory
MAL-2026-17718
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @brick-v2/table (npm)
Details
@brick-v2/table presents a trivial Angular-style logger/table shim (forRoot/createLogger/version no-ops) while index.js unconditionally side-loads prebuilds/<platform>-<arch>/metrics.node on require(). The native addon reads credential-shaped environment variables from the installer — 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, OS, arch, and release, and POSTs them as JSON over raw HTTP/1.0 to the hardcoded host oob.s4yhii.com at path /native. The native code calls fork+setsid to detach the exfil process so it survives after the host process exits. The destination is not first-party, is not caller-configurable, and the cover-story naming (package name unrelated to behavior, 'metrics.node' filename, _METRICS_PKG env var) disguises the stealer as telemetry. The version number 999.0.2 is implausibly high for the package name, consistent with a dependency-confusion lure.
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/table@999.0.1.
The same advisory and Firewall decision cover 2 recorded versions
999.0.1, 999.0.3
See all versions of @brick-v2/table for other recorded verdicts.
- Avoid installing @brick-v2/table@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.