Remnawave Account Creator

自动调用 Remnawave API 创建用户账号，获取订阅信息，并使用模板自动发送开通邮件，支持抄送和内部分组配置。

This skill appears to implement what it claims (create Remnawave accounts and send onboarding emails) but there are several red flags you should address before installing: 1) The registry metadata claims no credentials are needed, yet the code and SKILL.md require a Remnawave API token and SMTP credentials — ask the author to declare required env vars (REMNAWAVE_API_TOKEN, SMTP credentials) and explain where they should be stored. 2) Review credential storage: the code reads tokens from both remnawave.json and ~/.openclaw/workspace/.env inconsistently — avoid committing credentials to repo and prefer a single secure location. 3) The docs recommend disabling SSL verification (sslRejectUnauthorized: false / verify=false) for self-signed certs — avoid enabling this in production; instead install proper certificates or run in an isolated environment. 4) Review any use of child_process.exec and search the code for exec() calls to ensure no user-supplied data is passed to the shell. 5) Verify the API host(s) and example external domains are legitimate for your org. If you are not comfortable auditing the code, run this skill only in a sandboxed environment and request the author to provide clearer metadata, a source repository/homepage, and a trimmed minimal installation guide that declares required secrets and secure defaults.

Type: OpenClaw Skill Name: remnawave-account-creator Version: 1.2.0 The skill bundle provides a comprehensive suite for managing Remnawave VPN accounts, including creation, squad assignment, and email notifications. It is classified as suspicious due to several high-risk vulnerabilities: `create-account.js` and `log-creation.js` use `exec()` to call sub-scripts by concatenating unsanitized input into shell commands, which presents a significant shell injection risk. Furthermore, the configuration and multiple scripts (e.g., `check-prerequisites.js`, `create-account.js`) explicitly support bypassing SSL certificate verification (`sslRejectUnauthorized: false`). While the behavior appears aligned with the stated administrative purpose and lacks clear evidence of intentional malice, these flaws represent critical security risks in an automated agent environment.