T09 · Insecure Skill Coding Practices
- Location
SKILL.md:84- Finding
Apify API Token Exposed in URL Query Parameter
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent Instagram hashtag analysis helper, but users should avoid the REST example that puts an Apify token in the URL.
Install only if you are comfortable sending requested Instagram hashtags or URLs to Apify and using an Apify account token. Avoid copying the REST fallback as written unless you change it to pass the token in an Authorization header, and use a narrowly scoped token where possible.
SKILL.md:84Apify API Token Exposed in URL Query Parameter
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
REST API fallback:
curl -X POST "https://api.apify.com/v2/acts/apidojo~instagram-scraper/runs?token=$APIFY_TOKEN" -H "Content-Type: application/json" -d '{"keywords": ["#[hashtag1]", "#[hashtag2]"], "maxItems": 50}'
Run per hashtag (or in batch if MCP supports multiple hashtags in one run).
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
REST API fallback:
curl -X POST "https://api.apify.com/v2/acts/apidojo~instagram-scraper/runs?token=$APIFY_TOKEN" -H "Content-Type: application/json" -d '{"keywords": ["#[hashtag1]", "#[hashtag2]"], "maxItems": 50}'
Run per hashtag (or in batch if MCP supports multiple hashtags in one run).
No suspicious patterns detected.