@telora/daemon@0.21.156
Agent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe source supports a warning for agent configuration setup and refresh, but not a confirmed attack. The configuration setup is explicit-command driven and the manifest has no install-time lifecycle hook.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the connect command; later daemon startup may refresh Claude settings.
Impact
These changes can affect the instructions, permissions, hooks, or registered tools available to configured AI clients.
Mechanism
The package seeds or merges agent instruction files, permissions and hooks, and Telora MCP registrations.
AI rationale
The source supports a warning for agent configuration setup and refresh, but not a confirmed attack. The configuration setup is explicit-command driven and the manifest has no install-time lifecycle hook.
Evidence
dist/cli/connect.jsdist/cli/connect/agents.jsdist/cli/connect/claude.jsdist/cli/connect/ide.jsdist/cli/connect/codex.jsdist/cli/connect/cline.js.claude/settings.jsonAGENTS.md.cursor/mcp.json.vscode/mcp.json.mcp.json~/.codex/config.toml
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The explicit connect flow seeds configuration for multiple AI agent and IDE clients.
- Its writers add or merge agent instruction files and Claude settings, and register Telora MCP configurations.
- The package can refresh Claude settings during daemon startup.
Evidence against
- The manifest has only a prepublishOnly lifecycle script, not an install-time hook.
- The configuration changes are invoked through connect; several writers preserve existing content and skip unchanged writes.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcedist/update/self-update.jsView file
21*/
L22: import { execFileSync, execFile } from 'node:child_process';
L23: import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync } from 'node:fs';
High
Child Process
Package source references child process execution.
dist/update/self-update.jsView on unpkg · L2112* Three installation modes:
L13: * - **npm**: Installed globally via `npm install -g @telora/daemon`.
L14: * Updates via `npm install -g @telora/daemon@latest`.
...
L21: */
L22: import { execFileSync, execFile } from 'node:child_process';
L23: import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync } from 'node:fs';
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
dist/update/self-update.jsView on unpkg · L12dist/verify/verification-baseline.js#virtual:normalized:round1View file
106
Findings
2 Critical4 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/shell/unified-shell.js
CriticalKnown Malicious Dependency Insertionpackage.json
HighChild Processdist/update/self-update.js
HighShelldist/verify/verification-baseline.js#virtual:normalized:round1
HighRuntime Package Installdist/update/self-update.js
HighSemantic Analysis Limiteddist/cli/connect.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/telora-daemon-wrapper.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Low
Affected versions and remediation
This report applies to @telora/daemon@0.21.156.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.21.156 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.