registry / @ricsam/r5d-browser / 0.0.194-prod.1792097540715.g2cf87b4b4b2cee3802a201ee05a3f3f2c8629640
@ricsam/r5d-browser@0.0.194-prod.1792097540715.g2cf87b4b4b2cee3802a201ee05a3f3f2c8629640
`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-aiThe scanner’s execution and process findings correspond to page-level browser automation and launching a validated local Chrome executable. The inspected code sends credentials to the resolved HTTPS service and shows no separate malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
An operator runs the CLI start command to connect the browser client.
Impact
No unrelated credential recipient, install-time mutation, or other concrete attack effect was established.
Mechanism
The client authenticates to its resolved HTTPS service, processes returned browser actions, and can run JavaScript in the current page through its run_js capability.
AI rationale
The scanner’s execution and process findings correspond to page-level browser automation and launching a validated local Chrome executable. The inspected code sends credentials to the resolved HTTPS service and shows no separate malicious behavior.
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 entrypoint and contains no lifecycle script.
- Starting the client resolves its configured connection and requires an HTTPS origin.
- The request helper sends bearer credentials to routes under that same resolved origin.
- The client checks the returned resource identity before processing service actions; its polling, forwarding, receipt and acknowledgement callers all use that request helper.
- Dynamic code execution is part of the browser-page run_js capability and is reported as an escape hatch, not run at install time.
- The launcher validates a local Chrome executable before spawning it, while the navigation observer watches matching main-frame navigations.
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.1792097540715.g2cf87b4b4b2cee3802a201ee05a3f3f2c8629640.
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.1792097540715.g2cf87b4b4b2cee3802a201ee05a3f3f2c8629640 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.