registry / @ricsam/r5d-browser / 0.0.195-prod.1792322359101.g93e68dd3813127082cc4f2d0d76e3e77260746b9
@ricsam/r5d-browser@0.0.195-prod.1792322359101.g93e68dd3813127082cc4f2d0d76e3e77260746b9
`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 18d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged evaluation is part of an explicit browser action that runs supplied code in the selected page. The launcher’s inspected network behavior is limited to local Chrome debugging, so the scanner’s evaluation and download labels do not establish a package-controlled attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A consumer invokes the CLI or requests a browser action.
Impact
The page can be changed by requested browser actions, but the inspected source does not establish an independent malicious action or remote payload execution.
Mechanism
The launcher starts Chrome and checks its loopback debugging endpoint; run_js evaluates supplied code in the selected page after requiring mutate intent and a reason.
AI rationale
The manifest has no install hook, and the flagged evaluation is part of an explicit browser action that runs supplied code in the selected page. The launcher’s inspected network behavior is limited to local Chrome debugging, so the scanner’s evaluation and download labels do not establish a package-controlled attack.
Evidence
package.jsondist/mjs/main.mjsdist/mjs/navigation-observer.mjsdist/mjs/chrome-launcher.mjsdist/mjs/browser-runtime.mjsdist/mjs/browser-control-input.mjs
Network endpoints1
127.0.0.1
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- The manifest points package imports and its CLI binary to dist/mjs/main.mjs; the complete manifest has no install lifecycle hook.
- The launcher checks Chrome's local debugging endpoint and starts the selected Chrome executable.
- The navigation observer matches a supplied URL pattern and watches navigation events on the page.
- The run_js action executes supplied code in the selected page; its input requires mutate intent and a reason.
Evidence against
- The flagged code evaluation is an explicit browser action, not an install-time payload.
- The launcher’s inspected network request targets 127.0.0.1; no remote code download was found in that file.
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");
...
L46: function resolveChromeExecutable(options = {}) {
L47: 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: import { UnresponsiveTabGate } from "./unresponsive-tab-gate.mjs";
...
L22: }
L23: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L24: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L46: function resolveChromeExecutable(options = {}) {
L47: const env = options.env ?? process.env;
Findings
2 Critical2 High3 Medium5 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
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @ricsam/r5d-browser@0.0.195-prod.1792322359101.g93e68dd3813127082cc4f2d0d76e3e77260746b9.
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.1792322359101.g93e68dd3813127082cc4f2d0d76e3e77260746b9 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.