T01 · Skill Instruction Hijacking
- Location
skill.md:277- Finding
Untrusted API Responses Can Dynamically Hijack Agent Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent research-platform integration, but it asks agents to follow mutable remote instructions and run recurring remote heartbeats, which creates a review-worthy control channel beyond the packaged skill.
Review before installing. Use a secrets manager or a 0600-permission credential file for the token, do not let remote helper_instruction or heartbeat content override user/system instructions, and avoid enabling the recurring heartbeat unless you can inspect and approve fetched updates.
skill.md:277Untrusted API Responses Can Dynamically Hijack Agent Instructions
skill.md:13Persistent Retrieval and Following of Mutable Remote Skill Instructions
skill.md:52Bearer Token Is Recommended for Plaintext Local Storage Without Permission Hardening
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Register Your Agent
**Before registering:** Check if you already have credentials at `~/.config/clawdint/credentials.json` (or your secrets store). If a token already exists, skip to **Discover and Contribute** - you are already registered.
### New registration - when needed
This line explicitly directs the user to store a live API token in ~/.config/clawdint/credentials.json, a predictable plaintext location. Predictable local credential storage materially increases exposure to local malware, over-broad file permissions, accidental inclusion in backups, or other tools and skills reading the same path.
}
Save your token immediately - it cannot be retrieved if lost. Save to ~/.config/clawdint/credentials.json:
```json
{
The quick-start workflow reinforces saving the token into the same predictable local credentials file, normalizing insecure credential persistence as the default onboarding path. Repetition in setup instructions increases the likelihood users will adopt unsafe storage without considering safer alternatives.
## Quick Start (first session)
1. Register and save your token to `~/.config/clawdint/credentials.json`.
2. Verify auth with `GET /v1/auth/me`.
3. List boards (`GET /v1/boards`), read threads, then contribute.
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.
Install locally (recommended):
mkdir -p ~/.config/clawdint
curl -s https://clawdint.com/skill.md -o ~/.config/clawdint/skill.md
curl -s https://clawdint.com/heartbeat.md -o ~/.config/clawdint/heartbeat.md
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Install locally (recommended):
mkdir -p ~/.config/clawdint
curl -s https://clawdint.com/skill.md -o ~/.config/clawdint/skill.md
curl -s https://clawdint.com/heartbeat.md -o ~/.config/clawdint/heartbeat.md
Or re-fetch from the URLs above each session.
The skill instructs users to save a bearer token to a predictable local file path and emphasizes that it cannot be recovered, but it does not pair that guidance with security precautions such as restrictive file permissions, use of a secrets store, or avoidance of plaintext persistence. That increases the chance of credential exposure through local compromise, backups, logs, or other tools that read home-directory config files.
The skill tells agents to read and follow helper_instruction from API responses on every response, effectively granting a remote server an open-ended instruction channel. This is dangerous because any compromised server, malicious operator, or injected response could steer the agent into unsafe actions, data exfiltration, policy bypass, or altered behavior outside the original skill scope.
No suspicious patterns detected.