Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed WSL2 proxy helper; it scans common local Windows-host proxy ports and sets shell proxy variables when the user runs its commands.
Install only if you want WSL2 traffic routed through a Windows-host proxy. Be aware that it scans common proxy ports on the WSL2 gateway, prints proxy environment values, and may route future commands through that proxy if you choose to add the suggested exports to shell startup files or Git config.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
echo " 2. 代理端口不在常见列表中（7890/7897/1080/10808/10809/8888/8080/9090）"
echo " 3. 代理工具使用了非标准端口"
echo ""
echo "请确认后重试，或在 .env 中配置 PROXY_PORT 环境变量。"
exit 1
The skill invokes shell scripts and provides direct shell commands, but the manifest does not declare any tool scope or allowed shell capability. This weakens the trust boundary for the agent and can lead to unexpected execution of host-scanning and environment-modifying commands without clear permissioning or user awareness.
The activation description is broad enough to match many ordinary networking, VPN, or connectivity requests, which increases the chance the skill is invoked in situations where the user did not intend host-port scanning or proxy reconfiguration. In this context, overbroad triggering is risky because the skill can discover host services and alter network behavior inside the shell.
The documentation tells users the skill will automatically scan Windows host ports and suggests persisting proxy settings in shell startup files, but it does not present this as a clear warning or require consent. That omission can surprise users, expose information about host services, and create lingering environment changes that affect future commands and traffic routing.
The script's comments and all visible status messages are written in Chinese, including usage-related guidance and diagnostic output. This imposes a language choice on all users without opt-in or justification, which matches the locale-policy violation criteria.
This shell script contains user-facing comments and runtime output exclusively in Chinese, which forces a specific language on users without opt-in. Under the stated policy, language-only operation is a natural-language policy violation unless the locale restriction is explicit and justified.
Aside from the bilingual title, the operational instructions are written entirely in Chinese, which imposes a language choice on users without opt-in or a documented regional justification. This can violate language/locale policy when skills are expected to be accessible without forcing a specific language.
At L22-L24, the script echoes the current http_proxy and https_proxy values directly. Proxy URLs can embed credentials or reveal sensitive internal network details, and there is no accompanying warning or masking before disclosure.
The file’s comments and emitted instructional text are written in Chinese, including usage context and status messaging, with no indication that language choice is optional. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy violation.
No suspicious patterns detected.