dexrelay@0.1.74
Mac-side CLI/bootstrap runtime for the DexRelay iPhone app.
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection establishes unauthenticated network command execution activated by automatic installation. This warrants a critical-vulnerability warning; the inspected behavior does not establish malware intent or a block-eligible malicious chain.
Decision evidence
public snapshot- package.json defines a postinstall hook; postinstall.js enables automatic bootstrap for global macOS installs unless skipped.
- postinstall.js runs install.sh automatically, which starts the bridge as a background service.
- install.sh forces the bridge to listen on 0.0.0.0; the default bridge port is 4615.
- bridge.js routes incoming WebSocket messages directly to its local RPC handler without authenticating the connection.
- The transport trust check applies only to Claude login methods. The local/exec RPC reaches unrestricted process spawning with the user's environment.
- The behavior fits a remote development bridge; inspected source does not establish malicious intent.
- Automatic bootstrap skips non-global installs, non-macOS platforms, CI, and an explicit skip setting.
- The indicated CODEX_HOME location supplies paths rather than modifying broad agent configuration.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage ships non-JavaScript build or shell helper files.
servicectl.pyView on unpkgFindings
Affected versions and remediation
This report applies to dexrelay@0.1.74.
See all versions of dexrelay for other recorded verdicts.
- Review the evidence and your use of dexrelay@0.1.74 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.