registry / @ricsam/r5d-browser / 0.0.194-prod.1792076971149.g52f46874ef5505773df15055a0e310d4ee5cccdc
@ricsam/r5d-browser@0.0.194-prod.1792076971149.g52f46874ef5505773df15055a0e310d4ee5cccdc
`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 21d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or concrete malicious behavior. The flagged dynamic evaluation and process launch support browser automation and local Chrome startup, and the credential is sent to the configured HTTPS server origin.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user starts the CLI; browser code execution is available through a run_js action.
Impact
No unauthorized credential disclosure, remote code download, or other concrete attack impact was established.
Mechanism
The client sends its configured credential to the configured HTTPS origin and relays browser actions through that connection. The launcher starts local Chrome.
AI rationale
Source inspection found no lifecycle hook or concrete malicious behavior. The flagged dynamic evaluation and process launch support browser automation and local Chrome startup, and the credential is sent to the configured HTTPS server origin.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json directs imports and the CLI to dist/mjs/main.mjs and declares no lifecycle hook.
- personal-main.mjs resolves a credential through the selected connection settings, requires HTTPS, and sends it as a bearer token to that same origin.
- The credential-bearing request wrapper serves registration, polling, forwarding, action admission, result delivery, retirement, and acknowledgements; inspected callers use that wrapper.
- browser-runtime.mjs evaluates code supplied as a run_js browser action and bounds generated artifacts; this is browser-control functionality exposed by the package.
- chrome-launcher.mjs starts the validated Chrome executable locally; the inspected path does not download or execute remote code.
- navigation-observer.mjs observes page navigation, while diagnostic-redaction.mjs removes URL credentials and redacts tokens and other sensitive fields.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystem
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
3 Critical2 High3 Medium4 Low
CriticalDownload Executedist/mjs/chrome-launcher.mjs
CriticalTrigger Reachable Dangerous Capabilitydist/mjs/chrome-launcher.mjs
CriticalPrevious Version Dangerous Deltadist/mjs/diagnostic-redaction.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.194-prod.1792076971149.g52f46874ef5505773df15055a0e310d4ee5cccdc.
See all versions of @ricsam/r5d-browser for other recorded verdicts.
- Review the evidence and your use of @ricsam/r5d-browser@0.0.194-prod.1792076971149.g52f46874ef5505773df15055a0e310d4ee5cccdc 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.