Security audit

wechat-toolkit

Security checks for vulnerabilities and agentic risk

Overview

The skill's code mostly matches its advertised functions (search/download/rewrites/publish), but the package metadata omits important runtime requirements and the scripts perform filesystem, network, and global-install actions that are not declared — this mismatch warrants caution.

This skill mostly does what it claims (search, download, rewrite, publish WeChat articles), but there are important inconsistencies and side-effects you should consider before installing: - Metadata vs reality: The registry says 'no required env vars', but publishing requires WECHAT_APP_ID and WECHAT_APP_SECRET (or those values stored in TOOLS.md under your home). The skill reads your home directory to find credentials and will write a token cache (~/.config/wenyan-md/token.json). - Undeclared host requirements: The downloader needs Google Chrome installed (scripts probe common install paths) — this is mentioned in README/SKILL.md but not enforced in the declared binaries list. - Auto-modifying your system: publish.js will try to auto-install @wenyan-md/cli globally (npm -g) if missing; downloader/publisher require npm installs. These global installs modify your environment. - Filesystem access: scripts read and write files outside the skill folder (home folder TOOLS.md, config cache), and will create output directories for downloads and previews. - Network & credentials: Publishing uses your WeChat credentials to call api.weixin.qq.com and performs media uploads. Provide only credentials you control and consider using a throwaway/test WeChat account if you want to test. Recommendations before use: - Inspect the code (you have full sources); confirm you are comfortable with reading/writing the listed paths and with global npm installs. - Provide minimal/test credentials or run in an isolated environment (VM or container) to limit scope. - Backup any TOOLS.md files and inspect them to ensure no unintended secrets will be picked up. - If you need the skill but want safer behavior, request the author to update registry metadata to declare WECHAT_APP_ID/SECRET, the need for Chrome, and to avoid automatic global installs (or at least prompt before installing). If you want, I can point out the exact lines where credentials are read/written and where global installs are invoked so you can review them before running.

Static analysis

Detected: suspicious.dangerous_exec, suspicious.env_credential_access

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: scripts/publisher/publish_with_video.js:235

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: scripts/publisher/publish.js:44

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: scripts/publisher/theme_catalog.js:51

Environment variable access combined with network send.

Critical

Code: suspicious.env_credential_access
Location: scripts/downloader/download.js:161