Back to skill

Security audit

ytapi-youtube-channel-analysis

Security checks for vulnerabilities and agentic risk

Overview

The channel analysis fits its stated purpose, but setup saves your API key for future sessions without clearly explaining or seeking approval for that lasting access.

Review credential setup before use. Prefer the existing connector or a dedicated key in a protected secrets store, and agree on its storage location and future-session access. Ensure temporary credential files are private and removed. Signup sends your email and verification code to YTAPI, and analysis consumes API credits.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (6)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
85% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/auth-setup.md (reported line 94)May include surrounding context.

md
2. Check it in the current session without printing it, for example
   `test -n "$YTAPI_API_KEY" && echo set`. If the session must be reloaded to
   see it, reload it or tell the user.
3. Delete the temporary files: `rm -f /tmp/ytapi-signup.json /tmp/ytapi-verify.json`.

The user can sign in at https://ytapi.dev/auth/login?utm_source=skill&utm_medium=auth-setup with the same email to
see usage, manage keys and buy credits.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 18)May include surrounding context.

md
homepage: https://ytapi.dev
    requires:
      bins:
        - curl
    primaryEnv: YTAPI_API_KEY
    envVars:
      - name: YTAPI_API_KEY

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 55)May include surrounding context.

bash
H="Authorization: Bearer $YTAPI_API_KEY"
B=https://api.ytapi.dev/v1

# Profile: subscriber and video counts, country, description
curl -s "$B/channels/CHANNEL" -H "$H"

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/auth-setup.md (reported line 37)May include surrounding context.

to request in one step.

bash
curl -s -X POST https://ytapi.dev/api/agent/signup \
  -H "Content-Type: application/json" \
  -d '{"email": "USER_EMAIL"}' \
  -o /tmp/ytapi-signup.json

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/auth-setup.md (reported line 60)May include surrounding context.

bash
TOKEN=$(sed -n 's/.*"signup_token":"\([^"]*\)".*/\1/p' /tmp/ytapi-signup.json)
curl -s -X POST https://ytapi.dev/api/agent/verify \
  -H "Content-Type: application/json" \
  -d "{\"signup_token\": \"$TOKEN\", \"code\": \"CODE\"}" \
  -o /tmp/ytapi-verify.json

The workflow persists the API key across sessions without warning the user about the storage location or ongoing credential availability.

Medium
Category
Output Handling
Confidence
90% confidence
Finding

The workflow requires durable credential storage and availability in future non-interactive sessions without first telling the user where the key will be stored or obtaining consent for persistence. Permitting shell profiles or general configuration files without access-control requirements can expose the key to unrelated processes, later agent sessions, or other local users if permissions are weak.

Content

No source excerpt is available for this finding.