@telora/daemon@0.23.5
Agent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe package has a concrete capability to write agent and project configuration, but the inspected caller is the explicit connect command and no automatic install-time mutation was found. This supports a warning for user-invoked agent configuration changes, not a publish block.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the telora-daemon connect command with a connect token.
Impact
These writes can alter the local agent configuration and project setup when the command is intentionally run.
Mechanism
The flow writes daemon configuration and harness-specific files, including agent instruction or settings files, then provisions the daemon.
AI rationale
The package has a concrete capability to write agent and project configuration, but the inspected caller is the explicit connect command and no automatic install-time mutation was found. This supports a warning for user-invoked agent configuration changes, not a publish block.
Evidence
dist/cli/connect.jsdist/cli/connect/agents.jsdist/cli/connect/claude.jsdist/cli/connect/config-write.js
Network endpoints1
api.syntelyos.com
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package has a prepublishOnly build hook, with no preinstall, install, or postinstall hook in its manifest.
- The connect command invokes a flow that writes daemon and harness configuration, including files used by agent tools.
- The self-update npm installation is exposed through the daemon's update flow, not its package installation hook.
Evidence against
- Agent configuration changes are reached through an explicit connect command that redeems a token; the source inspected does not show an automatic package-install trigger for these writes.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcedist/update/self-update.jsView file
27*/
L28: import { execFileSync, execFile } from 'node:child_process';
L29: 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 · L2717* Three installation modes:
L18: * - **npm**: Installed globally via `npm install -g @telora/daemon`.
L19: * Updates via `npm install -g --@telora:registry=<channel> @telora/daemon@latest`
...
L27: */
L28: import { execFileSync, execFile } from 'node:child_process';
L29: 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 · L17dist/verify/attribution/verification-baseline-run.js#virtual:normalized:round1View file
Findings
1 Critical4 High4 Medium6 Low
CriticalKnown Malicious Dependency Insertionpackage.json
HighChild Processdist/update/self-update.js
HighShelldist/verify/attribution/verification-baseline-run.js#virtual:normalized:round1
HighRuntime Package Installdist/update/self-update.js
HighSemantic Analysis Limiteddist/audit/audit-phase.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
LowWeak Cryptodist/completion/team-progress/team-progress-measure.js
Affected versions and remediation
This report applies to @telora/daemon@0.23.5.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.23.5 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.