registry / @ricsam/r5d-browser / 0.0.189-prod.1790432436302.g20f5390e5f835d2747b0dd9125992cf5e47ec012
@ricsam/r5d-browser@0.0.189-prod.1790432436302.g20f5390e5f835d2747b0dd9125992cf5e47ec012
`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-invoked Chrome keeper: it has no npm lifecycle hook, launches Chrome only from the CLI path, and authenticates to an HTTPS origin that defaults to the product host. Remote page JavaScript and loopback forwards are browser-control features of that started client, not a hidden install-time attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User runs the r5d-browser CLI, typically the start command.
Impact
Effects stay within the user-started browser session and that HTTPS API. No unsolicited credential harvest, persistence, or foreign agent-config mutation was found.
Mechanism
The client launches local Chrome and posts the supplied bearer token to the configured HTTPS r5d origin for registration and polling.
AI rationale
The package is a user-invoked Chrome keeper: it has no npm lifecycle hook, launches Chrome only from the CLI path, and authenticates to an HTTPS origin that defaults to the product host. Remote page JavaScript and loopback forwards are browser-control features of that started client, not a hidden install-time attack.
Network endpoints1
r5d.dev
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 exposes only the user CLI bin r5d-browser and has no install lifecycle scripts or self-dependency.
- Chrome is started with spawn of a resolved local Chrome executable and explicit launch arguments when the keeper runs.
- run_js is an explicit browser action that evaluates supplied page code through Playwright page.evaluate, not at install or import.
- The personal client accepts only an HTTPS origin, defaulting to https://r5d.dev, and sends the caller token to that origin.
Evidence against
- A remote poll can request browser actions, including page JavaScript and loopback port forwards, after the user starts the client.
- The bearer token and base URL can come from flags, environment, or the private r5d config rather than a hard-coded host allowlist.
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.1790432436302.g20f5390e5f835d2747b0dd9125992cf5e47ec012.
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.1790432436302.g20f5390e5f835d2747b0dd9125992cf5e47ec012 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.