registry / @ricsam/r5d-browser / 0.0.195-prod.1793255633793.g4b35271b7ec26c19128bff21074675cb5273ed63
@ricsam/r5d-browser@0.0.195-prod.1793255633793.g4b35271b7ec26c19128bff21074675cb5273ed63
`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 7d ago · by lpm-firewall-aiThe flagged process execution and dynamic evaluation support the stated browser-control purpose: the CLI launches locally installed Chrome and evaluates requested code in a browser page. Credentials are sent over HTTPS to the configured r5d server, with no evidence in the inspected paths of unrelated exfiltration or concealed downloading.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user invokes the CLI, such as with the start command, and connects it to an r5d server.
Impact
No malicious behavior was identified in the inspected paths; browser actions are part of the package’s stated purpose.
Mechanism
The client authenticates to the configured HTTPS origin, launches local Chrome, and handles browser actions including JavaScript execution in a page.
AI rationale
The flagged process execution and dynamic evaluation support the stated browser-control purpose: the CLI launches locally installed Chrome and evaluates requested code in a browser page. Credentials are sent over HTTPS to the configured r5d server, with no evidence in the inspected paths of unrelated exfiltration or concealed downloading.
Evidence
~/.r5d/personal-browser/<origin-hash>/<configured root>/chrome-profile<configured root>/downloads
Network endpoints1
Configured HTTPS r5d server (default https://r5d.dev)
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a browser CLI entry point; starting the browser is an explicit command.
- Credentials are read for the selected r5d connection, which must use HTTPS; bearer requests go to that origin’s personal-resource routes.
- Chrome is launched from a locally resolved executable with a dedicated profile and local debugging port; the launcher does not download a browser.
- The runtime can evaluate JavaScript in a page as the browser_run_js action, consistent with its remote browser-control purpose.
- The CLI documents https://r5d.dev as its default server and supports an explicit --base-url.
Evidence against
- Dynamic JavaScript execution and credential transport are powerful capabilities, but the inspected code uses them in the browser-control workflow and sends credentials to the configured r5d server.
- The scanner’s download_execute finding is not supported by the launcher source inspected; it resolves and launches an existing Chrome executable.
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.1793255633793.g4b35271b7ec26c19128bff21074675cb5273ed63.
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.1793255633793.g4b35271b7ec26c19128bff21074675cb5273ed63 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.