debug-mode

No direct evidence of overt malware (e.g., keylogging, reverse shell, cryptomining, or direct data exfiltration) is present in this module. However, there is a significant supply-chain risk: the code executes `npx -y chrome-devtools-mcp@latest` at runtime and can write MCP config pointing to `npx ...@latest`, enabling dependency drift/compromise risk. Additionally, it starts an external collector script (assets/collector.py) and can terminate processes/delete session directories. Network health checks are performed using host/port from collector.json, creating an SSRF-like probing possibility if an attacker can plant a spoofed session_dir in tempdir.

No clear evidence of malicious code (no outbound exfiltration, no command execution, no dynamic payload execution, no system modification outside its own session directory) is present in this module. The main security concerns are design-related: bearer-in-URL token authentication with no additional safeguards, permissive CORS/private-network headers, heuristic key-name-only secret filtering, and verbatim persistence of accepted JSON payloads to disk (plus potential DoS due to fsync per event). Overall: likely a benign debug collector, but high privacy/security risk if exposed or misconfigured.