T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:40- Finding
Unrestricted Direct-Message and Group Access
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This setup is not malicious, but it defaults to broad WeCom bot access while storing a bot secret locally and installing a mutable network-capable plugin.
Before installing, restrict WeCom access to known users or groups instead of using the open wildcard defaults, protect ~/.openclaw/openclaw.json with owner-only permissions, keep the bot secret out of repositories and shared backups, and prefer a pinned or otherwise verified plugin version when available.
SKILL.md:40Unrestricted Direct-Message and Group Access
SKILL.md:38Bot Secret Stored in Plaintext Configuration
SKILL.md:21Unpinned Installation of a Network-Capable Plugin
The skill directs the user to store a bot secret in plaintext inside a local JSON configuration file but does not warn that this credential is sensitive, should be protected with restrictive file permissions, and should not be committed, shared, or logged. While local config storage may be functionally required by the platform, the absence of handling guidance increases the risk of accidental credential disclosure through backups, screenshots, repo commits, or multi-user systems.