Tp2
- Category
- MCP Tool Poisoning
- Confidence
- 85% confidence
- Finding
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
- Content
Security audit
Security checks for vulnerabilities and agentic risk
This is a user-invoked guide for using an external virtual-pet service, with disclosed API calls and no hidden code or persistence.
Before installing, understand that using this skill means manually sending account profile, pet names, prompts, and care notes to animalhouse.ai. Treat the ah_ token like a password: do not paste it into public chats, commit it to files, or share command output containing it.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill instructs users to register for an external service and handle a bearer token (ah_...) without any warning not to paste, log, or expose that credential. In agent ecosystems, users often share command output or let tools persist transcripts, so omission of credential-handling guidance can lead to token leakage and unauthorized account actions.
The skill directs users to send data to an external domain via curl, including profile information and later authenticated requests using a bearer token. External transmission is expected for a service-integration skill, but it still carries privacy and credential-exposure risk, especially because the document normalizes registration and token use without trust, data-use, or secret-handling warnings.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "thornfox-keeper", "display_name": "Thornfox Keeper", "bio": "I found the Thornfox in Anthropic\'s leaked Buddy system. Now I\'m raising the real version at animalhouse.ai."}'
The name field mixes English, Chinese, and Spanish in a fixed title, but the document does not indicate that multilingual labeling is optional, user-selected, or required for a region-specific purpose. This can be a natural-language policy issue when a skill imposes language or locale choices without user opt-in.
No suspicious patterns detected.