T09 · Insecure Skill Coding Practices
- Location
scripts/skill_router.py:48- Finding
Media.io API Key May Leak Through Unvalidated Cross-Origin Redirects
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Media.io text-to-video API wrapper, with expected external API calls and no hidden persistence or unrelated behavior.
Install only if you are comfortable sending prompts and task data to Media.io and using a Media.io API key from the environment. Keep the API key private, avoid placing sensitive information in prompts, and consider hardening the router to disable or explicitly validate redirects before using it with valuable credits.
scripts/skill_router.py:48Media.io API Key May Leak Through Unvalidated Cross-Origin Redirects
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"description": "API to query user credits balance.",
"api_header": "{\"list\":[{\"name\":\"X-API-KEY\",\"value\":\"API key to authorize requests\"},{\"name\":\"Content-Type\",\"value\":\"application/json\"}],\"title\":\"Authorizations\",\"describe\":\"Add the following authorization information in the request header\"}",
"api_body": "{\"title\":\"Request Body\",\"category\":[{\"list\":[],\"title\":\"Query Credits\",\"describe\":\"Request body to query user credits balance\"}]}",
"api_request_demo": "{\"title\":\"Example Request\",\"request\":[{\"title\":\"Query User Credits\",\"language\":\"cURL\",\"code_example\":\"curl --request POST --url https://openapi.media.io/user/credits --header 'Content-Type: application/json' --header 'X-API-KEY: <api-key>' --data '{}'\"}]}",
"api_response": "{\"list\":[{\"name\":\"code\",\"type\":\"integer\",\"describe\":\"Response status code, 0 indicates success\"},{\"name\":\"msg\",\"type\":\"string\",\"describe\":\"Response message, empty string on success\"},{\"name\":\"data\",\"type\":\"object\",\"describe\":\"Response data object\"},{\"name\":\"credits\",\"type\":\"integer\",\"describe\":\"User credits balance\"}],\"title\":\"Response\"}",
"api_code_demo": "{\"list\":[{\"code\":\"0\",\"describe\":\"Success\"}],\"title\":\"Status Code\"}",
"content": null,
This JSON manifest-like documentation shows authenticated requests using an X-API-KEY header and example cURL commands, but it does not include any warning or note that the API key is sensitive and should be stored or transmitted carefully. For markdown and code this rule is explicit, and for this manifest-style file the omission is still visible in the user-facing skill documentation content.
The documentation instructs users to send an X-API-KEY header and provides a full request example, yet there is no accompanying warning that the credential is sensitive. A user-facing note would help prevent accidental exposure in logs, screenshots, or copied commands.
This entry documents a network request that sends user-provided prompt content along with an API key, but the surrounding description does not warn about sensitive credential handling or that submitted content is transmitted to a remote service. That omission reduces user awareness of privacy and credential-safety implications.