registry / @ricsam/r5d-browser / 0.0.194-prod.1792051159972.g11a4852341b5472cd17463dca777ba8c3a0659bb
@ricsam/r5d-browser@0.0.194-prod.1792051159972.g11a4852341b5472cd17463dca777ba8c3a0659bb
`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 21d ago · by lpm-firewall-aiThe flagged dynamic evaluation is used by the browser action runtime, and the launcher starts the resolved local Chrome executable. Credential requests use the same resolved HTTPS origin, with redirects disabled; no concrete malicious behavior was established.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs the browser CLI start command.
Impact
The connected service can control the selected browser workflow; inspected source does not show an unrelated credential recipient or an independent malicious chain.
Mechanism
The client sends authenticated requests to its resolved service origin and applies returned browser actions, including page JavaScript execution.
AI rationale
The flagged dynamic evaluation is used by the browser action runtime, and the launcher starts the resolved local Chrome executable. Credential requests use the same resolved HTTPS origin, with redirects disabled; no concrete malicious behavior was established.
Network endpoints1
r5d.dev
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes dist/mjs/main.mjs as the CLI entrypoint.
- The connection helper resolves the origin and credential from caller options, configuration, or environment, then requires HTTPS.
- Requests send the resolved bearer credential to that origin and disable redirects; inspected callers use the shared request helper for registration, polling, forwarding, and action receipts.
- The user-started polling loop validates relay identity before processing returned actions; run_js evaluates action code in the selected browser page as part of the browser-control workflow.
- The launcher spawns the resolved local Chrome executable, and the navigation observer watches page navigation events.
Evidence against
- The run_js action can execute code in a browser page, giving the connected relay substantial browser-control capability; the inspected path is part of the package’s browser client workflow.
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");
...
L46: function resolveChromeExecutable(options = {}) {
L47: 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: import { UnresponsiveTabGate } from "./unresponsive-tab-gate.mjs";
...
L22: }
L23: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L24: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L46: function resolveChromeExecutable(options = {}) {
L47: const env = options.env ?? process.env;
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.194-prod.1792051159972.g11a4852341b5472cd17463dca777ba8c3a0659bb.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.194-prod.1792051159972.g11a4852341b5472cd17463dca777ba8c3a0659bb 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.