registry / @ricsam/r5d-browser / 0.0.194-prod.1792062156831.gfeaa57300f1ac943d933121c9a9a2f1472a18c46
@ricsam/r5d-browser@0.0.194-prod.1792062156831.gfeaa57300f1ac943d933121c9a9a2f1472a18c46
`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 inspected entrypoint, credential route, relay callers, browser runtime, launcher, and navigation observer support the package’s browser-control function. The flagged evaluation runs supplied code in the page context, and the credential is sent to the configured HTTPS service origin; these facts do not establish a malicious attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user starts the browser client with its configured service and credential.
Impact
The inspected code supports browser control but establishes no separate malicious effect.
Mechanism
The client sends authenticated requests to the configured HTTPS origin, receives browser actions, and performs the requested browser operations.
AI rationale
The inspected entrypoint, credential route, relay callers, browser runtime, launcher, and navigation observer support the package’s browser-control function. The flagged evaluation runs supplied code in the page context, and the credential is sent to the configured HTTPS service origin; these facts do not establish a malicious attack.
Evidence
package.jsondist/mjs/main.mjsdist/mjs/personal-main.mjsdist/mjs/browser-runtime.mjsdist/mjs/chrome-launcher.mjsdist/mjs/navigation-observer.mjs
Network endpoints1
r5d.dev
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to the browser CLI entrypoint and declares no lifecycle hooks.
- The CLI starts the personal browser client; its origin and credential come from command-line options, environment, or client configuration, and the client requires HTTPS.
- The request helper sends the bearer token to that origin and rejects redirects; the cited relay callers register, poll, forward, and handle results for browser actions.
- The run_js operation evaluates the supplied code in a browser page as part of the browser runtime API.
- The launcher starts the resolved Chrome executable with constructed launch arguments.
- The navigation observer matches page URLs against the supplied pattern.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
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
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.194-prod.1792062156831.gfeaa57300f1ac943d933121c9a9a2f1472a18c46.
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.1792062156831.gfeaa57300f1ac943d933121c9a9a2f1472a18c46 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.