registry / @ricsam/r5d-browser / 0.0.195-prod.1792583878375.gf25747229b85cd86fb86742a74e8373e0001786f
@ricsam/r5d-browser@0.0.195-prod.1792583878375.gf25747229b85cd86fb86742a74e8373e0001786f
⚠ 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 15d ago · by lpm-firewall-aiThe inspected package source does not establish the scanner's claimed download-and-execute behavior. Required external dependency behavior, including the update client, remains unresolved, so this review cannot verify a clean result or confirm an attack.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Starting the CLI with automatic updates enabled, or using functionality that imports the unavailable dependencies.
Impact
The unresolved dependency behavior prevents a source-grounded clean verdict.
Mechanism
The CLI delegates updates to an external dependency; its update behavior could not be assessed from the available source.
AI rationale
The inspected package source does not establish the scanner's claimed download-and-execute behavior. Required external dependency behavior, including the update client, remains unresolved, so this review cannot verify a clean result or confirm an attack.
Evidence
package.jsondist/mjs/main.mjsdist/mjs/chrome-launcher.mjsdist/mjs/personal-main.mjsdist/mjs/browser-runtime.mjs
Decision evidence
public snapshotAI called this Manual Review at 76.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json declares @ricsam/r5d-api and playwright-core as dependencies, but their source was unavailable in the inspected package snapshot.
- The CLI invokes the external update client when its auto-update option is enabled.
- The visible Chrome launch code starts the configured Chrome executable directly.
- The visible connection code resolves caller or config settings and rejects non-HTTPS origins.
- The run_js action evaluates code in the browser page as an explicit browser action.
Evidence against
- The inspected Chrome launch path does not show a remote code download or shell command.
- The visible credential connection path requires HTTPS and resolves its origin from CLI, environment, or config inputs.
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: 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
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/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: 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) {
Findings
3 Critical2 High3 Medium4 Low
CriticalDownload Executedist/mjs/chrome-launcher.mjs
CriticalTrigger Reachable Dangerous Capabilitydist/mjs/chrome-launcher.mjs
CriticalPrevious Version Dangerous Deltadist/mjs/chrome-launcher.mjs
HighChild Processdist/mjs/chrome-launcher.mjs
HighEvaldist/mjs/browser-runtime.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.1792583878375.gf25747229b85cd86fb86742a74e8373e0001786f.
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.1792583878375.gf25747229b85cd86fb86742a74e8373e0001786f 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.