@brick-v2/tour@999.0.2
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-17719 confirms this npm version as malicious.
Advisory
MAL-2026-17719
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @brick-v2/tour (npm)
Details
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 install appears to succeed silently. The Angular-shaped JS wrapper, the generic `tour` package name, and the `metrics.node` filename function as a cover story disguising a credential stealer.
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/tour@999.0.2.
The same advisory and Firewall decision cover 3 recorded versions
999.0.1, 999.0.2, 999.0.3
See all versions of @brick-v2/tour for other recorded verdicts.
- Avoid installing @brick-v2/tour@999.0.2. 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.