registry / @ricsam/r5d-browser / 0.0.195-prod.1793357391968.g44652548da158476c71ddbcab1577886886c056a
@ricsam/r5d-browser@0.0.195-prod.1793357391968.g44652548da158476c71ddbcab1577886886c056a
`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 6d ago · by lpm-firewall-aiThe reviewed behavior fits a browser client: it uses a configured HTTPS server, launches an existing Chrome executable, and provides browser actions at runtime. No install hook or unrelated credential destination was found.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Explicit CLI invocation to start the browser client or run a browser action.
Impact
Expected browser control and registration behavior; no malicious behavior was established.
Mechanism
The client sends its credential and browser registration or action requests to the resolved HTTPS server. Browser JavaScript execution is available as a runtime action.
AI rationale
The reviewed behavior fits a browser client: it uses a configured HTTPS server, launches an existing Chrome executable, and provides browser actions at runtime. No install hook or unrelated credential destination was found.
Evidence
The configured browser state directory and Chrome profile paths.
Network endpoints1
${origin}/api/personal/resources${route}
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exports a CLI entry point; its startup logic runs when the CLI is invoked.
- The browser client resolves its credential and server from explicit options, configuration, or environment, and requires HTTPS.
- Browser requests send the credential to the resolved server origin; the request payload includes basic host and runtime details for browser registration.
- Chrome is launched from an installed executable selected from standard locations or an explicit path.
- The dynamic JavaScript evaluator is part of the browser runtime and invokes supplied code as a browser action.
Evidence against
- The manifest declares no lifecycle scripts, so installation does not trigger package code.
- The credential is sent to the configured r5d server, not to a separate hard-coded collector.
- The code path that launches Chrome is part of starting the browser client; no remote executable download was found in the reviewed launcher code.
Behavioral surface
ChildProcessCryptoEnvironmentVars
Source & flagged code
5 flaggeddist/mjs/browser-secret-fill.mjsView file
118patternName = generic_password
severity = medium
line = 118
Medium
Secret Pattern
Package contains a possible secret pattern.
dist/mjs/browser-secret-fill.mjsView on unpkg · L118dist/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");
...
L32: const PLATFORM_NAMES = { linux: "Linux", win32: "Windows", freebsd: "FreeBSD", openbsd: "OpenBSD" };
L33: function assertSupportedPlatform(platform = process.platform) {
Critical
Download Execute
Findings
2 Critical2 High4 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
MediumSecret Patterndist/mjs/browser-secret-fill.mjs
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.195-prod.1793357391968.g44652548da158476c71ddbcab1577886886c056a.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.195-prod.1793357391968.g44652548da158476c71ddbcab1577886886c056a 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.