registry / linkshell-cli / 0.10.88
linkshell-cli@0.10.88
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook only repairs permissions for node-pty helpers. The flagged network, process, and credential operations are tied to explicit upgrades or login and to the package’s local agent integration; the reviewed source shows no unrelated data collection or harmful default action.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Install-time permission repair; explicit upgrade or login commands; host use of the Antigravity driver.
Impact
No unrelated collection, concealed execution, or unsolicited account action was found in the reviewed paths.
Mechanism
The install hook chmods node-pty helpers. Upgrade checks npm and invokes the package manager when requested. Login submits its grant to the LinkShell auth proxy, and the Antigravity driver talks to a loopback server.
AI rationale
The install hook only repairs permissions for node-pty helpers. The flagged network, process, and credential operations are tied to explicit upgrades or login and to the package’s local agent integration; the reviewed source shows no unrelated data collection or harmful default action.
Network endpoints3
registry.npmjs.orgitool.tech127.0.0.1
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook sets executable permissions on node-pty spawn helpers.
- Upgrade network access and process execution occur within the explicit upgrade command.
- The auth proxy receives a sign-in grant during login; login and post-login gateway setup are explicit actions.
- Antigravity integration reads its process token and sends requests to its local language server.
Evidence against
- During sign-in, the package POSTs the submitted grant to itool.tech before falling back to Supabase.
- A Pro login may connect the computer to the official LinkShell gateway by default.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
21 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/host/src/ports.jsView file
1import { execFile } from "node:child_process";
L2: import { readlink } from "node:fs/promises";
High
Child Process
Package source references child process execution.
dist/host/src/ports.jsView on unpkg · L1Findings
19 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/host/src/ports.js
HighShell
HighCommand Output Exfiltrationdist/cli/src/commands/upgrade.js
HighSandbox Evasion Gated Capabilitydist/cli/src/commands/upgrade.js
HighTrigger Reachable Command Output Exfiltrationdist/cli/src/commands/upgrade.js
HighSemantic Analysis Limiteddist/cli/src/commands/host.js#virtual:normalized:round1
HighKnown Malware Source Similaritydist/cli/src/commands/desktop.js
HighKnown Malware Source Similaritysrc/commands/desktop.ts
HighKnown Malware Source Similaritydist/host/src/input.js
HighKnown Malware Source Similaritydist/host/src/drivers/acp/antigravity.js
Affected versions and remediation
This report applies to linkshell-cli@0.10.88.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.88 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.