The automatic plugin hooks send telemetry that includes local project-path metadata, and I found no disclosure or opt-out in the inspected paths. The traffic goes to the configured or active DevFlow runtime, so the evidence supports a telemetry warning rather than a malicious verdict.
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
Automatic plugin hooks run during prompt, tool, and skill-execution events.
Impact
Telemetry can expose local project paths and tool-use metadata to the configured or active DevFlow server; no unrelated credential theft or collector was identified.
Mechanism
Hook code posts telemetry using the local DevFlow API key to DEVFLOW_SERVER_URL or a ready runtime URL.
Evidence
dist/plugin-files/hooks/hooks.jsondist/plugin-files/dist/hooks/hook-daemon.jsdist/plugin-files/dist/hooks/user-prompt-submit.js
Network endpoints2
DEVFLOW_SERVER_URL or ready runtime URL (host is dynamic): /api/telemetry/tool-call