微信公众号内容提取工具

Extract metadata and content from WeChat Official Account articles. Use when user needs to parse WeChat article URLs (mp.weixin.qq.com), extract article info...

This skill mostly matches its description (it fetches and parses WeChat article pages), but take these precautions before installing or running it: - Inspect or remove helper scripts: do not run convert.js or run-extract.js unmodified — they contain hardcoded absolute paths that will read/write files in specific user home directories. Those files look like developer convenience scripts and are not needed for normal CLI usage. - Beware dynamic execution: scripts/extract.js uses new Function(...) to evaluate JavaScript taken from page <script> blocks. That can execute arbitrary code from the scraped page. Only run this tool on unprivileged hosts or inside a sandbox/container, and avoid feeding it URLs from untrusted sources. - Run in an isolated environment (VM, container) and avoid running as an administrator/root user. Review which files will be written and consider changing output paths to a safe directory. - If you need higher assurance, ask the maintainer whether the new Function usage is strictly limited to parsing static assignment expressions (and for a code comment or test showing sanitization), and request removal or disabling of developer scripts with hardcoded paths. Given these issues, treat the skill as suspicious rather than outright malicious; it may be benign developer leftovers, but it includes risky behaviors you should address before use.

Type: OpenClaw Skill Name: wechatarticle-extractor Version: 1.0.0 The skill contains a significant security vulnerability in `scripts/extract.js`, where it uses `new Function()` to execute JavaScript code extracted directly from the HTML of the target WeChat article. This creates a Remote Code Execution (RCE) risk if the tool is directed to a malicious URL designed to exploit this parsing logic. Additionally, `convert.js` and `run-extract.js` contain hardcoded absolute file paths (e.g., `/Users/canghe/` and `C:/Users/xsl/`), suggesting the bundle was packaged from a local development environment without proper sanitization. While these issues represent poor security practices and high risk, there is no clear evidence of intentional malice or data exfiltration.