registry / @ricsam/r5d-browser / 0.0.189-prod.1790110688453.g0fa50f294b0a5116a01d86a56e4d1d2d0f9b33eb
@ricsam/r5d-browser@0.0.189-prod.1790110688453.g0fa50f294b0a5116a01d86a56e4d1d2d0f9b33eb
`r5d-browser start --auto-update` enables automatic client updates for this environment and state directory. The setting persists; `--no-auto-update` disables it. The client checks the authenticated environment's selected release once a minute and stages
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package is a user-started macOS Chrome client for an r5d account, with no install hooks and no hidden credential or payload path. Remote page script and loopback forwards are explicit relay features of that CLI, not an unconsented attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User invocation of r5d-browser start or an absolute private keeper config, not package install or import of a library API.
Impact
Effects stay within the stated personal-browser product: a dedicated Chrome profile and account relay. No unconsented harvest, exfiltration, or install mutation was found.
Mechanism
The client launches local Chrome, authenticates to the configured HTTPS r5d origin, and applies relay actions including optional page JavaScript in that browser.
AI rationale
The package is a user-started macOS Chrome client for an r5d account, with no install hooks and no hidden credential or payload path. Remote page script and loopback forwards are explicit relay features of that CLI, not an unconsented attack.
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no install lifecycle scripts. The only entry is the user-run bin r5d-browser pointing at dist/mjs/main.mjs, which acts only after CLI arguments.
- Chrome is spawned from a resolved local executable with a dedicated profile. The launcher refuses the daily-driver Chrome directory and talks only to a loopback DevTools port it opened.
- Page JavaScript runs only inside an already launched browser when the authenticated personal relay sends a run_js action after the user starts the client.
Evidence against
- The bearer token is sent only to the HTTPS origin from the CLI, environment, or private r5dctl config, defaulting to https://r5d.dev, as authentication for that r5d API.
- Port forwards bind 127.0.0.1 and ::1 and only after the user starts the client and the same account relay returns forward definitions.
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: const DEFAULT_STARTUP_TIMEOUT_MS = 15e3;
...
L21: }
L22: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L23: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L45: function resolveChromeExecutable(options = {}) {
L46: const env = options.env ?? process.env;
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/personal-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: const DEFAULT_STARTUP_TIMEOUT_MS = 15e3;
...
L21: }
L22: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L23: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L45: function resolveChromeExecutable(options = {}) {
L46: const env = options.env ?? process.env;
Findings
2 Critical3 High3 Medium4 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
HighSemantic Analysis Limiteddist/mjs/browser-runtime.mjs#virtual:string-array:round1
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.189-prod.1790110688453.g0fa50f294b0a5116a01d86a56e4d1d2d0f9b33eb.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.189-prod.1790110688453.g0fa50f294b0a5116a01d86a56e4d1d2d0f9b33eb 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.