T09 · Insecure Skill Coding Practices
- Location
SKILL.md:85- Finding
Apify API Token Exposed in URL Query Strings
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill’s Apify search behavior matches its purpose, but its REST fallback places the Apify token in URL query strings, which can expose the credential in logs or process listings.
Review before installing or following the REST fallback. Prefer Apify MCP or helper tooling that keeps secrets out of URLs, or change the documented curl examples to use an authorization header. Use a least-privilege Apify token and rotate it if it may have appeared in logs, shell history, or copied diagnostics.
SKILL.md:85Apify API Token Exposed in URL Query Strings
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~google-search-scraper/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"searchTerms": ["[SECTOR] acquisition 2026", "[SECTOR] acquired", "[COMPANY] acquires"], "maxItems": 100}'
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~google-search-scraper/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"searchTerms": ["[SECTOR] acquisition 2026", "[SECTOR] acquired", "[COMPANY] acquires"], "maxItems": 100}'
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~google-search-scraper/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"searchTerms": ["[SECTOR] acquisition 2026", "[SECTOR] acquired", "[COMPANY] acquires"], "maxItems": 100}'
No suspicious patterns detected.