@telora/daemon@0.22.52
Agent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package is not proven malicious, but its remote-driven permission-bypassing agent execution, configuration writes, hooks, and automatic self-update create substantial unresolved risk. Its only publish lifecycle hook is prepublishOnly, so the stricter install-hook blocking rule does not apply.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running telora-daemon after configuration, or invoking telora-daemon connect.
Impact
A compromised Telora control plane or malicious accepted request could direct a permission-bypassing Claude process in a configured repository; installed hooks run on later Claude events.
Mechanism
Remote-driven agent spawning, Claude hook configuration, and global self-updating.
AI rationale
The package is not proven malicious, but its remote-driven permission-bypassing agent execution, configuration writes, hooks, and automatic self-update create substantial unresolved risk. Its only publish lifecycle hook is prepublishOnly, so the stricter install-hook blocking rule does not apply.
Evidence
dist/update/self-update.jsdist/shell/unified-shell.jsdist/shell/unified-shell-provisioning.jsdist/cli/connect/registration.jsdist/nexus/intake-spawn.js.claude/settings.json~/.claude/settings.json.telora/daemon.jsonglobal npm installation
Network endpoints1
api.syntelyos.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The daemon starts an automatic updater and installs its latest global package release.
- A running daemon can create or modify Claude project settings across configured repositories.
- The connect command adds executable PostToolUse and UserPromptSubmit hooks to the user's Claude settings.
- Remote intake data is supplied to a Claude process launched with permission checks disabled.
Evidence against
- package.json has no install, preinstall, or postinstall lifecycle hook.
- The risky configuration flow is reached through explicit connect or daemon-run commands rather than package installation.
- The inspected code contains no direct credential harvesting or secret exfiltration logic.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcedist/update/self-update.jsView file
25*/
L26: import { execFileSync, execFile } from 'node:child_process';
L27: 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 · L2516* Three installation modes:
L17: * - **npm**: Installed globally via `npm install -g @telora/daemon`.
L18: * Updates via `npm install -g @telora/daemon@latest`.
...
L25: */
L26: import { execFileSync, execFile } from 'node:child_process';
L27: 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 · L16dist/verify/verification-baseline.jsView file
116}
L117: /** Spawn `sh -c command` in cwd and capture the FULL combined stdout+stderr. */
L118: function runShellCapture(command, cwd, timeoutMs) {
Findings
2 Critical4 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/nexus/intake-spawn.js
CriticalKnown Malicious Dependency Insertionpackage.json
HighChild Processdist/update/self-update.js
HighShelldist/verify/verification-baseline.js
HighRuntime Package Installdist/update/self-update.js
HighSemantic Analysis Limitedbuild-info.json
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/telora-daemon-wrapper.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Low
Affected versions and remediation
This report applies to @telora/daemon@0.22.52.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.22.52 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.