T09 · Insecure Skill Coding Practices
- Location
references/api.md:21- Finding
Phone Number Exposed in a GET Request Query String
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill does what it says by checking a phone number with an external WhatsApp-check API, but users should know queried numbers are sent to that provider.
Use this skill only when you are comfortable sending the queried phone number to wa-check-api.whatsabot.com or the configured MCP service. Avoid checking numbers without authorization or doing bulk enumeration, keep the API key in a protected secret store, and prefer deployments with clear retention, redaction, and abuse-control policies.
references/api.md:21Phone Number Exposed in a GET Request Query String
The manifest and body say to use the skill when the user asks to check whether a number 'has WhatsApp' or 'is using WhatsApp,' with several example phrasings but no explicit boundaries or negative examples. This can cause unintended invocation for general conversational mentions of WhatsApp and does not specify when the skill should not activate.
The skill instructs sending a user-supplied phone number to an external third-party API without warning about the data disclosure or obtaining informed consent. Because phone numbers are personal data, silently transmitting them can create privacy, compliance, and trust risks, especially in environments where users may assume processing is local.
This API reference documents sending phone numbers to a third-party service to determine whether they are registered on WhatsApp, but it provides no privacy, consent, retention, or lawful-use guidance. Phone numbers are personal data, and exposing a lookup workflow without data-handling warnings increases the risk of unauthorized enumeration, privacy violations, and noncompliant processing under applicable privacy laws or platform policies.
No suspicious patterns detected.