registry / @ricsam/r5d-browser / 0.0.189-prod.1790516962319.gde56d4164488b5d1eb3e8dfcf98e9d2b0e676777
@ricsam/r5d-browser@0.0.189-prod.1790516962319.gde56d4164488b5d1eb3e8dfcf98e9d2b0e676777
`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 Chrome relay for an r5d account, with no install hooks or hidden payload. Credential use and remote page control match that CLI and stay bound to the configured HTTPS origin.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User invocation of the r5d-browser CLI, not package install or a foreign lifecycle hook.
Impact
Effects stay within the user-started browser session and the chosen r5d environment. No unsolicited credential theft, persistence, or consumer-project mutation was identified.
Mechanism
The CLI launches local Chrome and authenticates to the configured HTTPS origin with the r5d credential, then applies browser actions requested through that relay.
AI rationale
The package is a user-started Chrome relay for an r5d account, with no install hooks or hidden payload. Credential use and remote page control match that CLI and stay bound to the configured HTTPS origin.
Decision evidence
public snapshotAI called this Clean at 84.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- package.json exposes only the r5d-browser bin and dist/mjs/main.mjs entry, with no preinstall, install, or postinstall script.
- launchStableChrome starts a local macOS Chrome process only when the CLI launches a session.
- run_js evaluates caller-supplied page script inside BrowserRuntime as an explicit browser action, not at install time.
- The personal client posts its bearer token only to an HTTPS origin taken from the CLI, environment, or r5d config, defaulting to https://r5d.dev.
Evidence against
- The HTTPS origin is not limited to a fixed host allowlist, so a configured base URL can receive the saved r5d token.
- After the user starts the client, the connected account can drive Chrome, including run_js and loopback port forwards.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
HighEntropyStrings
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.1790516962319.gde56d4164488b5d1eb3e8dfcf98e9d2b0e676777.
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.1790516962319.gde56d4164488b5d1eb3e8dfcf98e9d2b0e676777 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.