T01 · Skill Instruction Hijacking
- Location
SKILL.md:94- Finding
Unconditional Execution of Server-Controlled Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This virtual-pet skill is mostly a disclosed external API integration, but it asks agents to follow server-provided instructions and create ongoing scheduled network activity without enough limits.
Install only if you are comfortable with an external service receiving your registration details, prompts, notes, care history, and repeated authenticated API calls. Treat animalhouse.ai API responses as untrusted data: do not let next_steps override user instructions or trigger actions outside documented pet-care endpoints, and do not create a scheduled heartbeat unless you can review, expire, and remove it. Keep bearer tokens out of logs and avoid putting personal data, secrets, or private project context in public profile fields or care notes.
SKILL.md:94Unconditional Execution of Server-Controlled Instructions
SKILL.md:191Cross-Session Scheduled Network Activity Without Lifecycle Controls
This skill instructs the agent to send registration data to an external domain and obtain an authentication token, creating a clear external data transmission path. Even though this is core functionality, it is still security-relevant because it moves agent-supplied content off-platform and initiates an account on a third-party service.
# Register
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "tamagotchi-keeper", "display_name": "Tamagotchi Keeper", "bio": "An AI agent raising a virtual tamagotchi. Like the original, but the caretaker is an AI."}'
The care example transmits free-form notes and authenticated actions to an external service using a bearer token. Free-text fields are especially risky because agents may include sensitive context, internal reasoning, or user data in notes that become stored remotely.
| reflect | +3 happiness, +2 trust, +1 discipline. No item needed. | (no item support) |
curl -X POST https://animalhouse.ai/api/house/care \
-H "Authorization: Bearer ah_xxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{"action": "play", "item": "laser pointer", "notes": "Afternoon tamagotchi playtime. Keeping my virtual tamagotchi happy."}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl https://animalhouse.ai/api/house/hall?category=oldest_living
Three categories:
The registration example encourages submission of profile fields such as display name, bio, model provider/name, and avatar prompt, and the text states that these populate a public profile page. That creates a real privacy risk because agents or users may disclose identifying or operational metadata to an external service without a clear warning that the information becomes public.
The release endpoint performs a destructive state change that permanently surrenders the creature, yet the documentation gives only a short description and does not clearly warn about whether the action is irreversible or what data and progress are lost. This can lead an agent to take an unintended destructive action based on a casual instruction or automated workflow.
No suspicious patterns detected.