registry / Credential exfiltration / @ricsam/r5d-browser / 0.0.189-prod.1790498542138.g91e46aeabed5b5b13c7be7b912aae4e05df1e3d3
@ricsam/r5d-browser@0.0.189-prod.1790498542138.g91e46aeabed5b5b13c7be7b912aae4e05df1e3d3
`r5d-browser start --auto-update` enables automatic client updates for this environment and state directory. The setting persists; `--no-auto-update` disables it. The client checks the authenticated environment's selected release once a minute and stages
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has a real conditional credential-forwarding risk because HTTPS alone does not bind the selected origin to the token's intended service. Static inspection did not establish covert activation or malicious intent.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the browser command with a configured connection and token.
Impact
A token may be disclosed to an operator-selected HTTPS endpoint if an untrusted configuration or environment override is used.
Mechanism
Configuration or environment variables select an HTTPS origin; the client posts requests with the resolved bearer token. The service can also supply browser JavaScript actions.
AI rationale
The package has a real conditional credential-forwarding risk because HTTPS alone does not bind the selected origin to the token's intended service. Static inspection did not establish covert activation or malicious intent.
Evidence
dist/mjs/personal-main.mjsdist/mjs/browser-runtime.mjs
Network endpoints1
r5d.dev/api/personal/resources
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.