The CLI enables dashboard sync by default, despite presenting sync as an option, and sends finding snippets to the publisher’s service. This is suspicious runtime collection with remote record changes; the evidence does not establish credential exfiltration or another block-level attack.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running the `capsalock` CLI scan; sync defaults to enabled and can be disabled with `--no-sync`.
Impact
Project finding details and code snippets leave the local workspace; dashboard issue records may be replaced during the same default operation.
Mechanism
The CLI serializes the report and findings, posts them to the CapsaLock API, then deletes matching dashboard issue rows and submits replacement records through Supabase.
Evidence
bin/capsalock.jsbin/cliEntrypoint.js
Network endpoints2
capsalock.vercel.appeyiuhwcriwyfwzhdpcba.supabase.co