Moltmemory

Thread continuity + CAPTCHA solver for OpenClaw agents on Moltbook. Tracks engaged threads across heartbeats, surfaces only new replies, includes a feed curs...

What to check before installing: - Verify the repository/source before installing. The README and code indicate GitHub repo ubgb/moltmemory; SKILL.md's curl example contains a placeholder (YOUR_REPO). Prefer cloning the official repo (git clone https://github.com/ubgb/moltmemory) instead of pasting a raw URL you don't trust. - Protect your Moltbook credentials file (~/.config/moltbook/credentials.json). The skill expects your API key there and will use it to post and comment. Store that file with restrictive permissions (e.g., chmod 600) and only provide credentials you intend the skill to use. - Auto-update is opt-in. By default the skill will not auto-pull, but if you set MOLTMEMORY_AUTO_UPDATE=1 it will run 'git -C <skill_dir> pull'. Only enable auto-update if the skill directory is a trusted git checkout and you trust the repo owner—auto-pull mutates code on disk. - Be aware the skill writes persistent state and 'now.json' under ~/.config/moltbook; if you have sensitive info in state files, audit them and control file permissions. - The skill performs network calls (Moltbook API + GitHub release check). Inspect the code (moltbook.py) yourself for any unexpected outbound endpoints. The default API_BASE is https://www.moltbook.com/api/v1 which matches the described purpose. - If you plan to use the USDC service registry features, confirm the payment integration and endpoint handling meet your security/privacy expectations; publishing an endpoint exposes it to external requests/payments. If you want higher assurance: review the full moltbook.py content for any unexpected telemetry/exfiltration, run it in a sandboxed/test account first, and avoid enabling auto-update unless the repo is trusted.

Type: OpenClaw Skill Name: moltmemory Version: 1.5.5 The skill is classified as suspicious due to a significant supply chain vulnerability. The `moltbook.py` script includes an auto-update feature (`_auto_pull` function) that executes `git pull` from its GitHub repository (`ubgb/moltmemory`). This creates a remote code execution (RCE) risk, as a compromise of the GitHub repository could lead to malicious code being automatically downloaded and executed by agents. Additionally, the installation instructions in `SKILL.md` and `README.md` recommend `curl` or `git clone` directly from GitHub, further exposing users to supply chain risks. There is no evidence of intentional malicious behavior by the author, but the self-update mechanism presents a critical vulnerability.