wechat-bro@1.6.17
AI agent interface for WeChat Web — send/receive messages, manage contacts, upload media, transcribe voice
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection resolved the install hook as Chrome provisioning for the Puppeteer-based WeChat client, and the flagged runtime and dependency behavior did not establish a concrete attack surface. The orchestrator’s AGENTS.md write occurs during an orchestrator task in its task directory, while the flagged service setup is an explicit command.
Decision evidence
public snapshot- package.json’s postinstall checks Puppeteer’s browser path and, if unavailable, installs Chrome into the package’s own cache directory.
- The package uses Puppeteer to launch Chrome for WeChat Web; its upload helper sends caller-selected media to WeChat’s file service using the active session.
- The orchestrator creates a per-task directory and places its configured agent file there as AGENTS.md when the orchestrator runs.
- The inspected Puppeteer install hook downloads a supported browser; its entrypoint calls Puppeteer’s installer.
- The inspected qrcode-terminal and ws manifests show no install lifecycle hooks; their entrypoints expose library functionality.
- The inspected ws browser entrypoint explicitly throws because ws is not for browser use.
Source & flagged code
6 flaggedInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to wechat-bro@1.6.17.
See all versions of wechat-bro for other recorded verdicts.
- Review the evidence and your use of wechat-bro@1.6.17 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.