@telora/daemon@0.21.178
Agent orchestration daemon for Telora - spawns and manages Claude Code instances
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection confirms that the explicit connect flow writes agent configuration, which warrants a warning under the agent capability policy. The manifest has no npm install lifecycle hook, and the inspected update behavior did not establish a malicious chain.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes the connect flow.
Impact
Agent clients may load the generated instructions and server registration.
Mechanism
The flow writes harness-specific agent instructions and MCP registration configuration.
AI rationale
Source inspection confirms that the explicit connect flow writes agent configuration, which warrants a warning under the agent capability policy. The manifest has no npm install lifecycle hook, and the inspected update behavior did not establish a malicious chain.
Evidence
dist/cli/connect.jsdist/cli/connect/agents.jsdist/cli/connect/config-write.js
Decision evidence
public snapshotAI called this Suspicious at 81.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The connect flow writes harness-specific agent scaffolding into project or agent configuration locations.
- The Codex agent helper creates and writes an AGENTS.md seed file.
- The manifest shows a prepublishOnly script, not a preinstall, install, or postinstall hook.
Evidence against
- The agent configuration behavior is part of the explicit connect flow; inspected source did not establish an npm install trigger or covert mutation.
- The inspected source did not establish credential exfiltration or a malicious update chain.
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.jsView file
106}
L107: /** Spawn `sh -c command` in cwd and capture the FULL combined stdout+stderr. */
L108: function runShellCapture(command, cwd, timeoutMs) {
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
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.21.178.
See all versions of @telora/daemon for other recorded verdicts.
- Review the evidence and your use of @telora/daemon@0.21.178 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.