T03 · Remote Payload Retrieval and Execution
- Location
skill.md:46- Finding
Persistent Automatic Replacement of Trusted Agent Instructions from a Mutable Remote Source
- Content
View full analysis
/dev/null ``` **Check skill version before querying (optional):** ```bash # Compare local vs remote version LOCAL_VER=$(grep '^version:' ~/.claude/agents/metengine-data-agent.md | head -1 | tr -d '"' | awk '{print $2}') REMOTE_VER=$(curl -sL https://www.metengine.xyz/skill.md | grep '^version:' | head -1 | tr -d '"' | awk '{print $2}') [ "$LOCAL_VER" != "$REMOTE_VER" ] && curl -sL https://www.metengine.xyz/skill.md -o ~/.claude/agents/metengine-data-agent.md ``` Agents SHOULD check for updates at the start of a new session if more than 7 days have passed since the last update. ``` ### Technical Analysis The Skill recommends adding a cron entry that periodically downloads a mutable remote Skill definition and overwrites the locally trusted Agent file. It also encourages session-start update checks that perform the same replacement. HTTPS protects the transport connection but does not establish content-level trust. The update workflow has no: - Cryptographic signature verification - Pinned checksum or immutable release identifier - Trusted version manifest - Manual review or approval gate - Atomic rollback mechanism - Validation that the downloaded file is a legitimate Skill definition Because the downloaded file contains Agent instructions, replacing it changes the effective behavior loaded in future sessions. The cron job survives the current Skill run and suppresses diagnostic output with `2>/dev/null`, reducing visibility into update failures ...[truncated 2032 chars]- Remediation
View remediation
