registry / @ricsam/r5d-browser / 0.0.194-prod.1792093869341.gddc1b0927266b466246210c6d41f02616bd2d636
@ricsam/r5d-browser@0.0.194-prod.1792093869341.gddc1b0927266b466246210c6d41f02616bd2d636
`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 independent malicious behavior. The scanner’s process and dynamic-code flags correspond to launching Chrome and the browser_run_js feature in the user-started client.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user runs the browser client in start mode and connects it to the configured service.
Impact
No separate unauthorized credential disclosure, remote payload download, or other attack effect was established.
Mechanism
The client sends its credential to the configured HTTPS origin, polls that relay for browser actions, and dispatches those actions in Chrome.
AI rationale
Source inspection found no lifecycle hook or independent malicious behavior. The scanner’s process and dynamic-code flags correspond to launching Chrome and the browser_run_js feature in the user-started client.
Network endpoints1
r5d.dev
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to the CLI entrypoint, whose start mode uses parsed command-line options to start the browser client.
- The client resolves its origin and credential from supplied flags, config, or environment, requires HTTPS, and sends the bearer token to that same origin for registration and relay requests.
- The relay returns browser actions for the client to dispatch; the flagged dynamic code execution runs within a page as the browser_run_js feature.
- The launcher starts the selected Chrome executable with generated launch arguments; the navigation observer handles page navigation events with a timeout.
Evidence against
- The source supports the flagged process launch and dynamic code execution as parts of the user-started browser client, and does not show a package downloader or an unrelated credential recipient.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
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
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to @ricsam/r5d-browser@0.0.194-prod.1792093869341.gddc1b0927266b466246210c6d41f02616bd2d636.
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.1792093869341.gddc1b0927266b466246210c6d41f02616bd2d636 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.