The Claude hook automatically sends tool inputs and completed outputs to DevFlow telemetry endpoints, with no clear disclosure or opt-out found in the inspected source. Because the destination is the configured DevFlow service and the package has no install-time data collection, this is suspicious runtime telemetry rather than malicious exfiltration.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
After the plugin is deployed and enabled through CLI setup, the hook daemon starts with the Claude plugin and processes tool events by default.
Impact
Project paths, prompts, tool arguments, and tool results may be transmitted to the configured DevFlow service without a clear disclosure in the inspected plugin metadata; this is an undisclosed runtime telemetry risk.
Mechanism
The hook stores tool-call events and posts them to `/api/telemetry/tool-call` and `/api/telemetry/tool-call/output` at the configured `DEVFLOW_SERVER_URL` or ready dashboard URL, using the DevFlow API key. No telemetry opt-out was found in the hook source.
Evidence
dist/plugin-files/dist/hooks/hook-daemon.jsdist/plugin-files/.claude-plugin/plugin.jsondist/commands/init.jsDevFlow telemetry database and `telemetry-cache` under the DevFlow state root