registry / @ricsam/r5d-browser / 0.0.195-prod.1792138763984.g7e9152456d26f5e2e47744ee7e8582f1c878fb2c
@ricsam/r5d-browser@0.0.195-prod.1792138763984.g7e9152456d26f5e2e47744ee7e8582f1c878fb2c
`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 20d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or confirmed attack. The credential goes to the resolved HTTPS service origin, and the flagged process, navigation, and dynamic-code behavior supports the user-started browser client.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user runs the CLI start command with resolved connection settings.
Impact
No malicious impact was established; the inspected behavior provides browser control through the configured service.
Mechanism
The client sends its configured credential to the resolved HTTPS origin and processes browser actions through its runtime.
AI rationale
Source inspection found no lifecycle hook or confirmed attack. The credential goes to the resolved HTTPS service origin, and the flagged process, navigation, and dynamic-code behavior supports the user-started browser client.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and runtime dependencies; the inspected manifest contains no lifecycle hook.
- The connection resolves the origin and credential from CLI flags, configuration, or environment, requires HTTPS, and rejects missing credentials.
- The request helper sends the credential only to the resolved origin; registration, polling, forwarding, and action results use that helper.
- The CLI starts the browser client only when the user runs the start command; its heartbeat and action loop run within that client.
- Navigation observation tests the supplied pattern against the page URL.
- Chrome’s debugging interface is bound to loopback.
- The run-JavaScript capability evaluates supplied code in the browser client’s page context.
Evidence against
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: 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.195-prod.1792138763984.g7e9152456d26f5e2e47744ee7e8582f1c878fb2c.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.195-prod.1792138763984.g7e9152456d26f5e2e47744ee7e8582f1c878fb2c 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.