The package sends runtime monitoring data to its Puca-branded service, including tenant namespace and user-linked LLM usage metrics. The destination and token serve the monitor’s function, but the identifying telemetry warrants a warning.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
When MONITOR_TOKEN is configured, normal service startup initializes the monitor; application and LLM events are queued and flushed periodically.
Impact
The Puca monitoring service receives tenant namespace and user-linked usage information. No unrelated credential or file collection was identified.
Mechanism
The monitor formats metric tags and values, then posts them to monitor.puca.app using MONITOR_TOKEN as a bearer token.
Evidence
dist/essential/monitor.jsdist/essential/index.jsdist/core/services/llm/llm.service.jsdist/core/services/domain-life-cycle.service.js
Network endpoints2
monitor.puca.app/api/v2/write/api/webhooks/1379568992724713472/o-kY0nCxMsxN9GDcZ0RdX_5p16A_mUN4h7TWdrAqBIsSar5dLAvt4beZcrjbplpCAMgz