termdock@1.4.237
A complete web-based terminal application with modern UI
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource shows a real tmux/xterm terminal with package-aligned postinstall and user-invoked first-party agent hook setup, not an unconsented install-time hijack or self-dependency malware chain. The remaining risk is dual-use mutation of foreign agent configs after the product is running, which warrants a warning rather than a publish block.
Decision evidence
public snapshot- npm postinstall rebuilds node-pty and auto-installs tmux, including sudo system package managers.
- First-party installers write Termdock hooks into Claude, Codex, Copilot, OpenCode, Pi, Grok, and Kimi config paths.
- Server start rewrites already-installed stale hooks in those agent configs.
- A running-server HTTP route installs hooks for a chosen agent.
- Quota code reads local agent OAuth tokens and sends them to provider usage APIs.
- The running CLI can globally install termdock@<version> from npm as an updater.
- package.json has no runtime dependency on the termdock package name, so there is no nested self-install lifecycle chain.
- postinstall does not write agent configs; it only handles node-pty, tmux, and a ~/.termdock boot marker.
- Hook writes are marker-guarded and triggered by the product API or stale-refresh after the user already installed hooks, not by npm install.
- Discovered tokens are sent to official provider quota URLs such as api.anthropic.com, not to an unrelated collector.
- README and source describe a tmux/xterm web terminal; scanner malware-similarity labels look like prior-version routing, not a hidden payload in this tree.
Source & flagged code
30 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 source references child process execution.
dist/server/certificateWatcher.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to termdock@1.4.237.
See all versions of termdock for other recorded verdicts.
- Review the evidence and your use of termdock@1.4.237 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.