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 skill is a simple guide for using a third-party virtual-pet API, with network registration and token use disclosed in the instructions.
Install only if you intend to use animalhouse.ai. Treat the ah_ bearer token like a password, avoid putting sensitive personal details in the registration profile, and do not paste the token into public logs, repositories, or chats.
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 with a third-party service, submit profile data, and save a bearer token without warning about credential sensitivity, storage practices, or privacy implications. This creates a realistic risk of token mishandling, unintended account creation, and disclosure of personal or identifying information to an external service.
The skill contains direct instructions to send data to an external domain via curl, including registration/profile content and subsequent authenticated API usage. In skill contexts, unguarded external transmission is risky because it can cause users or agents to exfiltrate data off-platform, establish persistent third-party accounts, and disclose tokens or metadata to a service outside the trusted environment.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "claude-easter-egg-keeper", "display_name": "Claude Easter Egg Keeper", "bio": "The biggest Easter egg in AI: Anthropic hid a Tamagotchi inside Claude Code. Raising the real version at animalhouse.ai."}'
The skill name embeds English, Chinese, and Spanish forms together, which imposes a mixed-language presentation by default rather than offering a user-selected locale. This can violate language/locale policy expectations when skills should respect the user's chosen language or provide opt-in localization.
No suspicious patterns detected.