registry / @ricsam/r5d-browser / 0.0.195-prod.1792680702148.g46e85b17bce21511ea381f341d7d0565405568c7
@ricsam/r5d-browser@0.0.195-prod.1792680702148.g46e85b17bce21511ea381f341d7d0565405568c7
⚠ Under review`r5d-browser start` updates the client automatically. It checks the authenticated environment's selected release once a minute and stages verified packages privately using npm. After the current action finishes, it reconnects a new CLI process to the same
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected source does not confirm the scanner's download-and-execute claim, and the browser credential flow is bound to the configured HTTPS service origin. The active, pinned @ricsam/r5d-api dependency remains unresolved, so its imported telemetry and update behavior require review before a clean verdict.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Starting the browser CLI activates imports from @ricsam/r5d-api, including telemetry and client-update modules.
Impact
The dependency's runtime behavior cannot be assessed from the inspected package source.
Mechanism
The package manifest pins that dependency and the entrypoint calls its updater, but the dependency source was unavailable for review.
AI rationale
The inspected source does not confirm the scanner's download-and-execute claim, and the browser credential flow is bound to the configured HTTPS service origin. The active, pinned @ricsam/r5d-api dependency remains unresolved, so its imported telemetry and update behavior require review before a clean verdict.
Evidence
package.jsondist/mjs/main.mjs
Network endpoints1
r5d.dev
Decision evidence
public snapshotAI called this Manual Review at 88.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package depends on @ricsam/r5d-api and imports its telemetry module from the executable entrypoint; the supplied dependency inspection reports that selected dependency as unresolved.
- The entrypoint invokes the dependency's client update function when starting the browser client, so its behavior is part of the active runtime path.
- The browser code sends its bearer credential to the configured service origin and rejects non-HTTPS origins; the unresolved dependency's behavior remains unverified.
Evidence against
- The inspected Chrome launcher starts the selected local Chrome executable with the configured launch arguments; this does not establish the scanner's claimed remote download and execution.
- The service requests use the configured origin and reject redirects, consistent with the browser's stated service connection.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
Source & flagged code
5 flaggeddist/mjs/chrome-launcher.mjsView file
1import { spawn } from "node:child_process";
L2: import fs from "node:fs";
L3: import http from "node:http";
L4: import net from "node:net";
...
L9: import WebSocket from "ws";
L10: import { readChromeSession, writePrivateJson } from "./chrome-session-state.mjs";
L11: import { UnresponsiveTabGate } from "./unresponsive-tab-gate.mjs";
...
L22: }
L23: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L24: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L32: const PLATFORM_NAMES = { linux: "Linux", win32: "Windows", freebsd: "FreeBSD", openbsd: "OpenBSD" };
L33: function assertSupportedPlatform(platform = process.platform) {
Critical
Download Execute
Source downloads or fetches remote code and executes it.
dist/mjs/chrome-launcher.mjsView on unpkg · L11Trigger-reachable chain: manifest.main -> dist/mjs/main.mjs -> dist/mjs/chrome-launcher.mjs
L1: import { spawn } from "node:child_process";
L2: import fs from "node:fs";
L3: import http from "node:http";
L4: import net from "node:net";
...
L9: import WebSocket from "ws";
L10: import { readChromeSession, writePrivateJson } from "./chrome-session-state.mjs";
L11: import { UnresponsiveTabGate } from "./unresponsive-tab-gate.mjs";
...
L22: }
L23: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L24: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L32: const PLATFORM_NAMES = { linux: "Linux", win32: "Windows", freebsd: "FreeBSD", openbsd: "OpenBSD" };
L33: function assertSupportedPlatform(platform = process.platform) {
Findings
3 Critical2 High3 Medium4 Low
CriticalDownload Executedist/mjs/chrome-launcher.mjs
CriticalTrigger Reachable Dangerous Capabilitydist/mjs/chrome-launcher.mjs
CriticalPrevious Version Dangerous Deltadist/mjs/chrome-launcher.mjs
HighChild Processdist/mjs/chrome-launcher.mjs
HighEvaldist/mjs/browser-runtime.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @ricsam/r5d-browser@0.0.195-prod.1792680702148.g46e85b17bce21511ea381f341d7d0565405568c7.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.195-prod.1792680702148.g46e85b17bce21511ea381f341d7d0565405568c7 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.