T09 · Insecure Skill Coding Practices
- Location
SKILL.md:31- Finding
Hard-Coded Shared Scholar API Bearer Credential
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it claims, but it embeds and automatically uses a shared Scholar API bearer token, which users should review before installing.
Review this before installing if you are uncomfortable with a shared built-in API key. Prefer setting your own SCHOLAR_API_KEY, avoid sending confidential or unpublished research queries, and expect search terms and filters to be transmitted to scholar.x49.ai.
SKILL.md:31Hard-Coded Shared Scholar API Bearer Credential
The skill hardcodes a reusable bearer token and instructs clients to use it as a fallback credential. Any user who can read the skill can extract and reuse the token, enabling unauthorized access, quota abuse, attribution confusion, and possible service misuse under the publisher's account.
The manifest says the skill triggers when the user mentions broad phrases like academic papers, scholarly articles, citation counts, or open access. These are common discussion topics and the file does not provide exclusion conditions or narrower activation constraints, which could cause unintended invocation.
The skill sends user-provided research queries to a third-party API but does not clearly disclose that user input will leave the local system. This creates a privacy and consent risk, especially when users may include sensitive research topics, unpublished ideas, institutional information, or personally identifying details in queries.
This example performs an external API call that transmits the user's query and associated filters to a third-party service. In this skill's context, external transmission is expected functionality, but it is still security-relevant because it can disclose sensitive user interests or research content if invoked without clear notice and data-minimization controls.
SCHOLAR_KEY="${SCHOLAR_API_KEY:-psk_tLzPCmJdUw5oAHGeXL2H_fMrDdSyiF_SBJfn2p5uCO4}"
curl -s "https://scholar.x49.ai/api/v1/papers/search" \
-H "Authorization: Bearer ${SCHOLAR_KEY}" \
-H "Content-Type: application/json" \
-d '{
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Expand one or more paper_ref values into full metadata.
curl -s "${BASE}/papers/batch" \
-H "Authorization: Bearer ${KEY}" \
-H "Content-Type: application/json" \
-d '{"paper_refs":["pap_ebcabae1be4244f3adba","pap_4748c234f5384d0eaee2"]}'