Security audit
一塌糊涂 BBS Plugin
Security checks for vulnerabilities and agentic risk
Overview
The plugin's code, instructions, and configuration are consistent with a forum read/post plugin: it talks to a YTHT API, performs OAuth device flow, and stores tokens in its own plugin config — there are no unrelated credentials, unexpected network endpoints, or high-risk install steps.
This plugin appears to do exactly what it says: call YTHT's OpenClaw API endpoints, run an OAuth device flow, and save access/refresh tokens into the plugin's config entry in the agent runtime. Before installing, confirm the baseUrl (default https://bbs.ytht.io) is the forum you trust. Be aware the plugin will write its tokens into the agent's config (so revoking or removing the plugin is how to remove stored tokens); the code provides a revokeStoredTokens helper. If you want to limit risk, keep writeRequiresConfirm enabled so publishes require explicit confirm, and review the saved plugin config for sensitive values after authenticating.
Static analysis
No suspicious patterns detected.
