Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Remnawave Robot
v1.0.6自动化管理Remnawave账号全生命周期，支持配置向导、账号创建、分组同步、账号查询、删除及批量操作，并发送邮件通知。
⭐ 0· 140·0 current·0 all-time
by@uepuer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The repository implements Remnawave account lifecycle operations (create/search/sync/delete/add-to-group, send email), which matches the skill description. However the skill metadata declared no required env vars / credentials while the code clearly requires an API token and SMTP credentials (it reads ../../.env for REMNAWAVE_API_TOKEN and config/smtp.json for SMTP). This metadata omission is an incoherence you should be aware of.
Instruction Scope
SKILL.md tells the operator to run setup.js and other scripts; the runtime instructions map to the provided scripts. But the docs and scripts encourage disabling SSL verification for a default API IP (apiBaseUrl default is an IP: 8.212.8.43 and sslRejectUnauthorized can be set true), which weakens TLS security. The code reads and writes ../../.env and writes logs under ../../logs (outside the skill folder), increasing the chance of touching shared files. Templates and docs include external subscription links (e.g., datat.cc and other domains) — verify those endpoints.
Install Mechanism
No external download/install spec; the package is instruction + code with a single npm dependency (nodemailer). No obscure remote install URLs or archive extraction were observed. You must run npm install locally to fetch nodemailer from the public registry (expected).
Credentials
The skill requires sensitive secrets in practice (Remnawave API token and SMTP username/password) but the registry metadata did not declare them. The code stores/reads credentials in files: config/smtp.json (contains SMTP auth) and ../../.env (REMNAWAVE_API_TOKEN). Storing plaintext SMTP credentials in config and writing/reading a workspace-level .env file can expose secrets to other tools or skills sharing that workspace.
Persistence & Privilege
Skill does not request always:true and does not alter other skills' configs. However it writes outside its own directory (../../.env and ../../logs/...), which gives it persistent footprint in the workspace root — this is allowed for configuration but increases attack surface if the workspace .env contains other secrets or is shared.
What to consider before installing
This package appears to implement the described Remnawave account-management functions, but it has practical and security issues you should address before installing or running it:
- Expect to provide two sensitive credentials: a Remnawave API token and SMTP credentials (username/password). The skill metadata did NOT list these — treat that as a red flag and verify externally before trusting the package.
- The scripts read/write ../../.env (workspace-level .env). That file may be shared by other tools; don't point this skill at a .env that contains unrelated secrets. Prefer a dedicated credentials file or isolated test workspace.
- SMTP credentials are kept in config/smtp.json in plaintext (though files are chmod 600). Consider using a dedicated mailbox with minimal privileges or an app-specific credential rather than a primary admin mailbox.
- Default/config examples suggest disabling SSL verification and an API base using a raw IP address; avoid setting sslRejectUnauthorized=true in production and confirm the API endpoint is legitimate.
- Several templates and docs reference external domains (datat.cc, third-party download URLs). Validate those URLs independently — they may host subscription links or third-party binaries.
- Run the code first in an isolated test environment (non-production account, isolated workspace) and audit the files it writes (../../.env and logs) before using on real production secrets.
- If you proceed, consider editing setup.js to change the .env path to a skill-local secure store, or store the REMNAWAVE_API_TOKEN in a dedicated credential manager rather than workspace .env.
If you want, I can produce a short checklist and safe setup steps (how to run in an isolated folder, how to create and use a throwaway SMTP account, or a suggested patch to avoid writing to ../../.env).Like a lobster shell, security has layers — review code before you run it.
latestvk974xgcne24eap9p06njdj6ms1835c4s
License
MIT-0
Free to use, modify, and redistribute. No attribution required.