registry / @ricsam/r5d-browser / 0.0.195-prod.1792411561086.g41b1019eacd11dbc4482fac6f3b83af769df60e7
@ricsam/r5d-browser@0.0.195-prod.1792411561086.g41b1019eacd11dbc4482fac6f3b83af769df60e7
`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 17d ago · by lpm-firewall-aiThe inspected entrypoint and runtime behavior are consistent with a browser-control CLI: it sends the configured credential to the selected HTTPS server and launches Chrome. The scanner’s evaluation match is an explicit page action, and the remote download-and-execute hint was not supported by the inspected launcher source.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user starts the browser CLI or invokes a browser action.
Impact
No unintended credential disclosure, remote payload execution, or other concrete attack effect was established.
Mechanism
The CLI connects to the selected HTTPS server, launches Chrome, and evaluates code only through the explicit browser action.
AI rationale
The inspected entrypoint and runtime behavior are consistent with a browser-control CLI: it sends the configured credential to the selected HTTPS server and launches Chrome. The scanner’s evaluation match is an explicit page action, and the remote download-and-execute hint was not supported by the inspected launcher source.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to the CLI entrypoint and declares no lifecycle script in the inspected package.json.
- The CLI resolves a server and credential from caller options, configuration, or environment; the connection code requires HTTPS.
- Registration sends the credential to that selected server, rejects redirects, and is called when the user starts the personal browser.
- The launcher starts the configured Chrome executable, while the navigation observer watches page navigation events.
- The flagged dynamic evaluation is a named browser action that requires caller-supplied code and evaluates it in the page.
Evidence against
- The reviewed credential flow targets the selected r5d server origin; no unrelated recipient or hidden credential transfer was found.
- The inspected download/execute hint did not match remote code fetching in the Chrome launcher; its process launch is for Chrome.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystem
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
2 Critical2 High3 Medium5 Low
CriticalDownload Executedist/mjs/chrome-launcher.mjs
CriticalTrigger Reachable Dangerous Capabilitydist/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
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @ricsam/r5d-browser@0.0.195-prod.1792411561086.g41b1019eacd11dbc4482fac6f3b83af769df60e7.
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.1792411561086.g41b1019eacd11dbc4482fac6f3b83af769df60e7 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.