registry / @ricsam/r5d-browser / 0.0.194-prod.1791174951663.g5660debf54d7649e6f1a445b2920f376ae9d8f34
@ricsam/r5d-browser@0.0.194-prod.1791174951663.g5660debf54d7649e6f1a445b2920f376ae9d8f34
`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 flagged process execution launches installed Chrome, and dynamic evaluation implements browser operations rather than a hidden host payload. Inspected source shows no concrete malicious chain; authentication and configurable service requests are consistent with the client’s functionality.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user invokes start or supplies a private browser keeper configuration.
Impact
Browser control and private state creation are expected functionality; no covert exfiltration or malicious installation behavior was established.
Mechanism
The client launches local Chrome, receives browser operations, and executes supplied JavaScript in browser pages.
AI rationale
The flagged process execution launches installed Chrome, and dynamic evaluation implements browser operations rather than a hidden host payload. Inspected source shows no concrete malicious chain; authentication and configurable service requests are consistent with the client’s functionality.
Network endpoints2
r5d.dev127.0.0.1
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no install lifecycle hooks or runtime self-dependency.
- The Chrome launcher spawns a validated local executable with a dedicated profile and loopback debugging.
- Browser JavaScript execution handles caller-provided code inside page.evaluate, consistent with browser automation.
- The CLI activates the personal browser through the start command or an explicit private configuration.
- Authentication requests target the configured service origin, reject redirects, and use service credentials; no unrelated recipient was identified.
- The configured Chromium factory verifies a private approval file against its expected digest and restricts browser traffic to approved loopback origins.
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: 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.194-prod.1791174951663.g5660debf54d7649e6f1a445b2920f376ae9d8f34.
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.1791174951663.g5660debf54d7649e6f1a445b2920f376ae9d8f34 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.