The flagged capture and agent-hook behavior is tied to explicit Litmus assessment commands; capture disclosures and consent checks are present, and the captured data goes to Litmus’s configured backend. The Node download path is also an explicit, prompted, hash-verified recovery flow.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
User runs `litmus init` or `litmus connect`; laptop capture additionally requires server enablement and consent.
Impact
No malicious impact identified; the disclosed feature records selected assessment activity for Litmus.
Mechanism
Assessment data and consented capture events use Litmus backend routes. Init installs Litmus agent hooks and scopes trust to the assessment folder.
Evidence
~/.claude/settings.json~/.codex/hooks.json~/.codex/config.toml~/.cursor/hooks.json~/.gemini/settings.json
Network endpoints4
litmushiring.comconfigured Litmus backend: /cli/laptop-capture/events