registry / @ricsam/r5d-browser / 0.0.194-prod.1791637507463.g40e9e1c0846f697fbb07fca4ab876e7515e3d213
@ricsam/r5d-browser@0.0.194-prod.1791637507463.g40e9e1c0846f697fbb07fca4ab876e7515e3d213
`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 26d ago · by lpm-firewall-aiInspected source does not support the scanner's remote download-and-execute claim: the launcher spawns Chrome, and browser evaluation occurs as a runtime page action. The manifest has no install lifecycle hook, and the inspected token request targets the selected HTTPS service origin.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Use of the browser CLI or personal browser client.
Impact
These inspected behaviors support the package's browser automation purpose; no package-controlled payload execution or credential exfiltration was established.
Mechanism
The CLI launches Chrome; browser actions can evaluate caller-provided code in a page. The client sends its bearer token to the selected service origin.
AI rationale
Inspected source does not support the scanner's remote download-and-execute claim: the launcher spawns Chrome, and browser evaluation occurs as a runtime page action. The manifest has no install lifecycle hook, and the inspected token request targets the selected HTTPS service origin.
Evidence
dist/mjs/browser-runtime.mjs
Network endpoints1
r5d.dev
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a browser CLI and lists browser automation dependencies; no install lifecycle hook is present in the inspected manifest.
- The launcher starts the resolved Chrome executable with constructed launch arguments.
- The runtime evaluates JavaScript in a browser page and stores browser downloads under its configured downloads directory.
- The personal browser client defaults to the service origin and sends its bearer token to that origin's API endpoint.
Evidence against
- The reported download-and-execute behavior is not supported by the inspected launcher: its process spawn starts Chrome, and no download call was found there.
- The browser-page evaluation is part of a runtime browser action, not evidence of package-side arbitrary code execution at install or import time.
- The inspected credential request uses the selected HTTPS service origin, defaulting to r5d.dev.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystem
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.1791637507463.g40e9e1c0846f697fbb07fca4ab876e7515e3d213.
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.1791637507463.g40e9e1c0846f697fbb07fca4ab876e7515e3d213 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.