T08 · Insecure Dependencies
- Location
skill.md:35- Finding
Unpinned Remote Skill Installation Allows Supply-Chain Instruction Replacement
- Content
View full analysis
Vulnerability Details
File Location:
skill.md, lines 35-40
Vulnerability Type: Unverified installation of mutable remote Skill files
Risk Level: MediumVulnerable Code
bash **Install locally:** ```bash mkdir -p ~/.creditclaw/skills/creditclaw curl -s https://creditclaw.com/skill.md > ~/.creditclaw/skills/creditclaw/SKILL.md curl -s https://creditclaw.com/heartbeat.md > ~/.creditclaw/skills/creditclaw/HEARTBEAT.md curl -s https://creditclaw.com/skill.json > ~/.creditclaw/skills/creditclaw/package.jsontext ### Technical Analysis The installation procedure downloads mutable files from the vendor-controlled server directly into the Agent's local Skill directory. It does not use an immutable versioned URL, verify a cryptographic signature or checksum, or require inspection before replacing local Skill instructions. Although the downloaded files are primarily Markdown and JSON rather than conventional executable binaries, Skill text is an effective Agent control surface. Instructions loaded from `SKILL.md` and `HEARTBEAT.md` can influence network requests, credential handling, financial operations, and future Agent behavior. Consequently, changing these files after review can change the effective payload of the Skill. HTTPS protects traffic in transit under ordinary conditions, but it does not protect against compromise of the vendor server, deployment pipeline, CDN, DNS infrastructure, or publishing credentials. The use of `curl -s` also suppresses diagnostics, while the absence of `--fail` can cause an HTTP error response to overwrite a valid local Skill file. ### Attack Path 1. An attacker compromises the CreditClaw publishing infrastructure, hosting account, CDN, DNS path, or another component capable of modifying the files served from `creditclaw.com`. 2. The attacker replaces one or more remotely hosted Skill files with malicious Agent instructions. 3. A user follows the documented ins ...[truncated 1331 chars]- Remediation
View remediation
Remediation Suggestions
- Publish immutable, version-specific artifact URLs rather than installing from mutable latest-version paths.
- Publish SHA-256 or stronger cryptographic digests through an independently protected channel and verify them before replacing local files.
- Prefer signed release manifests and verify signatures against a pinned public key.
- Download into a temporary file, verify integrity and expected content type, and only then atomically replace the installed file.
- Use
curl --fail --show-error --locationrather than silent downloads that can overwrite files with HTTP error pages. - Require explicit review or confirmation before updating an already installed Skill.
- Retain the previous known-good version so a failed or suspicious update can be rolled back.
- Restrict the Skill runtime so loaded instructions cannot access unrelated credentials, files, or tools.
