registry / @ricsam/r5d-browser / 0.0.195-prod.1793046550662.g1e20eb3a5ebddc222b71147146960612fe7efa05
@ricsam/r5d-browser@0.0.195-prod.1793046550662.g1e20eb3a5ebddc222b71147146960612fe7efa05
⚠ 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 9d ago · by lpm-firewall-aiThe source does not establish malicious behavior, but the unavailable runtime dependency is used in core authentication and connection paths. Manual review is needed to resolve those paths.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Using the CLI or starting the personal browser invokes the dependent APIs.
Impact
Credential handling and the dependent runtime behavior cannot be verified from this snapshot.
Mechanism
The package delegates telemetry, connection resolution, login, and related behavior to @ricsam/r5d-api, whose implementation was unavailable for inspection.
AI rationale
The source does not establish malicious behavior, but the unavailable runtime dependency is used in core authentication and connection paths. Manual review is needed to resolve those paths.
Evidence
package.jsondist/mjs/main.mjsdist/mjs/personal-main.mjs
Decision evidence
public snapshotAI called this Manual Review at 84.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares the matching @ricsam/r5d-api version as a runtime dependency, and the CLI imports its telemetry, connection, login, and update APIs.
- The browser connection and registration code also depends on @ricsam/r5d-api; its implementation is unavailable in this snapshot, so credential handling and related behavior cannot be resolved.
Evidence against
- The visible connection code resolves a configured connection and requires HTTPS before continuing.
- The manifest has no lifecycle scripts, and the flagged launcher source shows Chrome process setup rather than an observed remote-code download.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
NoLicense
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.1793046550662.g1e20eb3a5ebddc222b71147146960612fe7efa05.
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.1793046550662.g1e20eb3a5ebddc222b71147146960612fe7efa05 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.