proxychains

[Skill Scanner] Installation of third-party script detected All findings: [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] [CRITICAL] command_injection: URL pointing to executable file detected (CI010) [AITech 9.1.4] [CRITICAL] command_injection: URL pointing to executable file detected (CI010) [AITech 9.1.4] [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] This skill is functionally coherent and implements a plausible helper: auto-retry network commands via proxychains4 and provide configuration snippets. It is not intrinsically malicious, but it carries a meaningful data-exfiltration risk: automatically routing arbitrary shell commands (including ones carrying credentials or tokens) through a proxy increases risk if the proxy is not strictly user-controlled and trusted. The automation rules that force proxying for popular package and code hosts (github/pypi/npm/docker) heighten this risk because they cause repeated, automatic routing of sensitive package-manager and Git traffic via the proxy. Recommend: treat the default proxy as untrusted until verified, avoid automatic proxying of commands that may expose credentials without explicit user consent, and add verification steps to ensure the proxy is local and trusted before automatic use.