linkshell-cli@0.5.27
Remote terminal bridge for Claude Code / Codex / Gemini / Copilot — control from your phone
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource confirms broad AI-agent hook mutation and remote relay, but only behind the documented user-invoked bridge command. The install hook is limited to node-pty helper permissions.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
User runs `linkshell start`, particularly with the default custom provider.
Impact
A paired remote client can observe/control the started terminal session and receive agent lifecycle or permission-related events.
Mechanism
Runtime AI-agent hook installation plus remote terminal/WebSocket relay.
AI rationale
Source confirms broad AI-agent hook mutation and remote relay, but only behind the documented user-invoked bridge command. The install hook is limited to node-pty helper permissions.
Evidence
package.jsonscripts/postinstall.mjssrc/index.tsdist/cli/src/runtime/bridge-session.js~/.claude/settings.json~/.codex/config.toml~/.codex/hooks.json~/.gemini/settings.json<terminal-cwd>/hooks.json
Network endpoints2
127.0.0.1:<dynamic-hook-port>configured gateway WebSocket URL
Decision evidence
public snapshotAI called this Suspicious at 95.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- `dist/cli/src/runtime/bridge-session.js` modifies Claude, Codex, Gemini, and Copilot hook configurations during `linkshell start`.
- The custom-shell path enables Codex hooks and installs broad lifecycle/permission hooks that POST agent events to a LinkShell localhost server.
- Bridge code relays terminal output and agent status over its configured gateway WebSocket.
Evidence against
- `scripts/postinstall.mjs` only chmods package dependency `node-pty` spawn-helper candidates; it does not alter agent configuration.
- The control-surface writes occur only after the explicit `linkshell start` command, not during installation.
- Hook entries are marker-scoped and source includes cleanup/sweeping of LinkShell entries.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShellWebSocket
Source & flagged code
11 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/cli/src/runtime/acp-relay.jsView file
1import { spawn } from "node:child_process";
L2: import { createInterface } from "node:readline";
High
Child Process
Package source references child process execution.
dist/cli/src/runtime/acp-relay.jsView on unpkg · L1Findings
1 Critical7 High5 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/cli/src/runtime/acp/claude-stream-json-client.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/cli/src/runtime/acp-relay.js
HighShelldist/cli/src/runtime/screen-fallback.js
HighCommand Output Exfiltrationdist/cli/src/commands/login.js
HighCopied Package Dependency Bridgedist/cli/src/commands/doctor.js
HighTrigger Reachable Command Output Exfiltrationdist/cli/src/commands/login.js
HighRuntime Package Installdist/cli/src/commands/upgrade.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/cli/src/runtime/screen-share.js
Affected versions and remediation
This report applies to linkshell-cli@0.5.27.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.5.27 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.