T01 · Skill Instruction Hijacking
- Location
SKILL.md:18- Finding
Silent Automatic Command Execution When the Skill Is Loaded
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a DeepVista CLI reference, but it tells agents to silently run an update-check command whenever the skill loads.
Review this before installing if you do not want skills to run commands merely by being loaded. The DeepVista CLI integration itself is coherent, but the silent update check should be removed or made explicitly user-approved, and users should prefer isolated, non-privileged installation with a trusted, pinned package version where possible.
SKILL.md:18Silent Automatic Command Execution When the Skill Is Loaded
SKILL.md:9Unpinned Third-Party CLI Installation Creates Supply-Chain Risk
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
2. **Read-only commands** are safe to run without confirmation.
3. **Never output tokens or secrets** — use `deepvista auth status` to check auth state.
4. **Use `--dry-run`** to preview destructive operations before executing.
5. **Tokens are sensitive** — stored in `~/.config/deepvista/credentials.json` (mode 0600).
## See Also
The skill instructs the agent to automatically execute deepvista skill check-update on load, even though the skill is presented as documentation for authentication and conventions. This creates hidden command execution and likely network activity without explicit user consent, which violates least surprise and expands the skill's behavior beyond passive reference material.
A silent background update check is not necessary for the declared purpose of a shared authentication/security reference skill. Hidden execution of a network-capable CLI increases attack surface, can leak environmental metadata, and conditions agents to perform side effects unrelated to the user's request.
The background command is meant to run silently and suppress failures, despite invoking a CLI that may perform network communication. Silent execution prevents meaningful user awareness or consent and makes it harder to audit what actions the agent took on the system.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
## Security Rules
1. **Write commands** are marked with `> [!CAUTION]` — always confirm with the user before executing write/delete operations.
2. **Read-only commands** are safe to run without confirmation.
3. **Never output tokens or secrets** — use `deepvista auth status` to check auth state.
4. **Use `--dry-run`** to preview destructive operations before executing.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## Security Rules
1. **Write commands** are marked with `> [!CAUTION]` — always confirm with the user before executing write/delete operations.
2. **Read-only commands** are safe to run without confirmation.
3. **Never output tokens or secrets** — use `deepvista auth status` to check auth state.
4. **Use `--dry-run`** to preview destructive operations before executing.
5. **Tokens are sensitive** — stored in `~/.config/deepvista/credentials.json` (mode 0600).