registry / terminal-commander / 0.3.9
terminal-commander@0.3.9
Terminal Commander: local MCP-operated terminal/file signal channel with native Linux, Windows, and macOS packages.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package automatically configures its own MCP integration during eligible installs, creating agent extension lifecycle risk. The inspected behavior is limited to this package’s named integration, so it does not establish a broader control-surface hijack or concrete malicious attack.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
An interactive, non-CI npm install without the package’s environment opt-outs.
Impact
Coding agents may start exposing this package’s local MCP tools after restart, without the user separately running setup.
Mechanism
The postinstall hook invokes bootstrap, which configures detected providers and forces the managed integration entry.
AI rationale
The package automatically configures its own MCP integration during eligible installs, creating agent extension lifecycle risk. The inspected behavior is limited to this package’s named integration, so it does not establish a broader control-surface hijack or concrete malicious attack.
Evidence
package.jsonscripts/postinstall.jslib/bootstrap/orchestrator.jslib/harness/write_all.jslib/cursor/config.js
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The npm postinstall hook runs an automatic bootstrap on interactive installs unless environment opt-outs are set.
- Bootstrap writes configuration for all detected provider harnesses and forces its managed entry during automatic setup.
- This behavior changes coding-agent MCP configuration without a separate setup command.
Evidence against
- The generated integration registers this package's own terminal-commander MCP server.
- The Cursor merge preserves other server entries and only replaces the package's named entry when forced.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
16 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkglib/cli/setup_cursor_wsl.jsView file
119Install-time code directly mutates a foreign AI-agent control surface:
L350: const text = serializeCursorMcpConfig({
L351: mcpServers: { [SERVER_NAME]: stanza },
L352: });
Write operation from lib/daemon/autostart.js:
L119: const dir = path.dirname(filePath);
L120: fs.mkdirSync(dir, { recursive: true });
L121: const tmp = path.join(dir, `.${path.basename(filePath)}.tmp-${process.pid}`);
L122: fs.writeFileSync(tmp, content, { encoding: "utf8", mode: mode || 0o644 });
L123: fs.renameSync(tmp, filePath);
Foreign user/project scope from lib/daemon/autostart.js:
L119: const dir = path.dirname(filePath);
L120: fs.mkdirSync(dir, { recursive: true });
L121: const tmp = path.join(dir, `.${path.basename(filePath)}.tmp-${process.pid}`);
L122: fs.writeFileSync(tmp, content, { encoding: "utf8", mode: m
Findings
1 Critical14 High4 Medium4 Low
CriticalAi Agent Control Hijacklib/cli/setup_cursor_wsl.js
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedbin/terminal-commanderd.js#virtual:normalized:round1
HighKnown Malware Source Similaritylib/cli/update_preflight.js
HighKnown Malware Source Similaritylib/daemon/autostart.js
HighKnown Malware Source Similaritybin/terminal-commander-mcp.js
HighKnown Malware Source Similaritylib/bootstrap/ensure_wsl_runtime.js
HighKnown Malware Source Similaritylib/cli/doctor_daemon.js
HighKnown Malware Source Similaritylib/cli/restart.js
HighKnown Malware Source Similaritylib/cli/setup_cursor_wsl.js
Affected versions and remediation
This report applies to terminal-commander@0.3.9.
See all versions of terminal-commander for other recorded verdicts.
- Review the evidence and your use of terminal-commander@0.3.9 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.