registry / @ricsam/r5d-browser / 0.0.195-prod.1792838121586.g0ea1a454c428970eca16754e9e7cc12c6143fa9f
@ricsam/r5d-browser@0.0.195-prod.1792838121586.g0ea1a454c428970eca16754e9e7cc12c6143fa9f
⚠ Under review`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 12d ago · by lpm-firewall-aiThe inspected source shows browser-launch functionality and origin-bound credential handling, with no confirmed attack behavior. The selected ws dependency source was unavailable after an inspection attempt, so the runtime path remains unresolved.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user starts the browser client, which uses the WebSocket dependency while controlling Chrome.
Impact
The unresolved dependency behavior prevents a complete assessment of this runtime path.
Mechanism
The launcher passes a Chrome debugger endpoint to the WebSocket client; the dependency implementation was unavailable for review.
AI rationale
The inspected source shows browser-launch functionality and origin-bound credential handling, with no confirmed attack behavior. The selected ws dependency source was unavailable after an inspection attempt, so the runtime path remains unresolved.
Evidence
package.jsondist/mjs/chrome-launcher.mjs
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares ws, which the Chrome launcher imports and uses to open a WebSocket; its selected dependency source was unavailable for inspection.
- The browser client sends its credential to the configured service origin, and saved credentials are refused when their recorded origin differs.
- The launcher starts the configured Chrome executable; the inspected code does not show a remote code download.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
NoLicense
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.1792838121586.g0ea1a454c428970eca16754e9e7cc12c6143fa9f.
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.1792838121586.g0ea1a454c428970eca16754e9e7cc12c6143fa9f 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.