registry / @ricsam/r5d-browser / 0.0.194-prod.1791558700852.g74b78427e042a397fce1e77846098e7977cfc5dc
@ricsam/r5d-browser@0.0.194-prod.1791558700852.g74b78427e042a397fce1e77846098e7977cfc5dc
`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 25d ago · by lpm-firewall-aiThe inspected behavior is activated through the CLI and aligns with controlling a persistent Chrome profile and relaying browser actions to an HTTPS r5d service. The flagged dynamic execution runs caller-supplied page code, while no package install hook or separate attack behavior was identified.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes the CLI start command or requests a browser action.
Impact
These inspected behaviors support the stated browser automation flow; no independent malicious execution or credential exfiltration path was established.
Mechanism
The CLI launches Chrome and can execute caller-provided JavaScript in a browser page; it sends a bearer token to the selected HTTPS r5d origin.
AI rationale
The inspected behavior is activated through the CLI and aligns with controlling a persistent Chrome profile and relaying browser actions to an HTTPS r5d service. The flagged dynamic execution runs caller-supplied page code, while no package install hook or separate attack behavior was identified.
Evidence
dist/mjs/chrome-launcher.mjsdist/mjs/browser-runtime.mjsdist/mjs/personal-main.mjs
Network endpoints1
r5d.dev
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares runtime dependencies but no install lifecycle scripts.
- Chrome is launched with the configured Chrome executable when the CLI runs.
- Dynamic code execution receives caller-supplied code and runs inside the browser page.
- The relay chooses a configured or default HTTPS origin and sends its bearer token to that origin.
Evidence against
- The package validates the relay origin as HTTPS and rejects URL credentials.
- Relay requests use the configured origin and disable redirects.
- The dynamic execution is explicitly tied to browser-page code, consistent with browser automation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
NoLicense
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: const DEFAULT_STARTUP_TIMEOUT_MS = 15e3;
...
L21: }
L22: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L23: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L45: function resolveChromeExecutable(options = {}) {
L46: 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: const DEFAULT_STARTUP_TIMEOUT_MS = 15e3;
...
L21: }
L22: function defaultChromeProfilePath(homeDirectory = os.homedir()) {
L23: return path.join(homeDirectory, ".r5d", "browser", "chrome-profile");
...
L45: function resolveChromeExecutable(options = {}) {
L46: const env = options.env ?? process.env;
Findings
2 Critical3 High3 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
HighSemantic Analysis Limiteddist/mjs/browser-runtime.mjs#virtual:string-array:round1
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.1791558700852.g74b78427e042a397fce1e77846098e7977cfc5dc.
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.1791558700852.g74b78427e042a397fce1e77846098e7977cfc5dc 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.