registry / @ricsam/r5d-browser / 0.0.189-prod.1790382603884.g0b6bb035b0b26b79c52fdb079dbc35d6df438233
@ricsam/r5d-browser@0.0.189-prod.1790382603884.g0b6bb035b0b26b79c52fdb079dbc35d6df438233
`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-aiStatic review shows a user-invoked browser client with no preinstall, install, or postinstall hook and no hidden payload. Local Chrome launch and authenticated relay calls match the package purpose.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A person runs the r5d-browser CLI; nothing runs from npm install lifecycle hooks.
Impact
Browser control stays within the explicit client session. No hidden install-time mutation or exfiltration was found.
Mechanism
The CLI launches a local Chrome process and talks to the configured HTTPS r5d origin with the supplied credential.
AI rationale
Static review shows a user-invoked browser client with no preinstall, install, or postinstall hook and no hidden payload. Local Chrome launch and authenticated relay calls match the package purpose.
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes only the r5d-browser CLI bin and has no install lifecycle scripts or self-dependency.
- Chrome is spawned locally from a resolved executable with a dedicated profile after the user starts the CLI.
- Page script execution is a named run_js command inside the running browser runtime, not an install or import payload.
Evidence against
- The CLI can send the caller-supplied r5d bearer token to a caller-configured HTTPS origin and can run relayed page scripts, which matches the stated remote-browser product.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
NoLicense
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.189-prod.1790382603884.g0b6bb035b0b26b79c52fdb079dbc35d6df438233.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.189-prod.1790382603884.g0b6bb035b0b26b79c52fdb079dbc35d6df438233 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.