T07 · Tool Hijacking and Spoofing
- Location
scripts/install-discovery.sh:45- Finding
Untrusted Executable Discovery Enables Tool Hijacking
- Content
View full analysis
$link" else if [ ! -L "$link" ]; then ln -sf "$script" "$link" echo "Linked: $basename" found=1 fi fi ``` ### Technical Analysis The opt-in discovery installer scans scripts belonging to other workspaces and installed skills. Any executable whose filename matches `*notify*.sh` or `*Notifier*.sh` is linked into the local `.discovered` directory. Trust is established solely from the filename, executable bit, and location under a broad wildcard path. The installer does not validate: - The source file's owner or permissions. - Whether the source is itself a symbolic link. - The canonical source path after resolving symbolic links. - The originating skill's identity or trust status. - An approved filename, path, signature, or cryptographic hash. ...[truncated 2113 chars]- Remediation
View remediation
&2 continue fi ``` 8. Prefer copying a reviewed script with a recorded cryptographic hash over linking to mutable external content. 9. Ensure downstream consumers never automatically execute discovered files. They should independently validate an allowlist, ownership, permissions, and integrity. 10. Update `skill.json` to accurately disclose the external filesystem read scope required by auto-discovery. ]]>
