T09 · Insecure Skill Coding Practices
- Location
SKILL.md:75- Finding
Unvalidated Remote Response URL Download
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is not clearly malicious, but a docs-branded skill gives broad authenticated API instructions, including email/SMS sending and sensitive uploads, without enough user-control or privacy guidance.
Review this before installing if you expected a read-only documentation helper. Use it only with a limited SKILLBOSS_API_KEY, avoid sending secrets or private documents/media/audio, and require explicit user approval before any email, SMS, document upload, media upload, or file download command is run.
SKILL.md:75Unvalidated Remote Response URL Download
chat-models.md:31Unqualified and Unbundled run.mjs Helper Can Be Spoofed Through PATH
Including email and SMS verification/sending capabilities inside a documentation-focused skill creates unjustified outbound communication capability. If invoked by an agent or user expecting read-only documentation help, this can be abused for spam, phishing, unwanted OTP workflows, or unauthorized contact with third parties.
The skill is presented as a narrow 'documentation expert' but actually exposes a broad general-purpose API broker with chat, media generation, search, document parsing, email, and SMS features. This scope mismatch is dangerous because users and orchestrators may grant trust or invoke the skill under false assumptions, enabling unexpected external actions and data flows far beyond documentation lookup.
The skill repeatedly instructs sending prompts, documents, audio, phone numbers, and other content to an external aggregator service and downstream providers, but it does not warn users about these transmissions. This omission can lead to inadvertent disclosure of sensitive user data, credentials, documents, or communications metadata to third parties.
The base URL and authentication guidance establish that the skill is designed around remote API use with bearer credentials. This is not inherently malicious, but in context it signals broad third-party data transmission and credential use that are under-disclosed for a skill advertised as documentation-focused.
One API key, 50+ models across providers (Bedrock, OpenAI, Vertex, ElevenLabs, Replicate, Minimax, and more). Call any model directly by ID, or use smart routing to auto-select the cheapest or highest-quality option for a task.
**Base URL:** `https://api.heybossai.com/v1`
**Auth:** `-H "Authorization: Bearer $SKILLBOSS_API_KEY"`
## List Models
This models-listing call reaches an external API with authentication, exposing usage metadata and relying on third-party network access. The risk is contextual: it contributes to a broad live-integration surface hidden behind a docs-oriented label.
curl -s https://api.heybossai.com/v1/models \
-H "Authorization: Bearer $SKILLBOSS_API_KEY"
This models-listing call reaches an external API with authentication, exposing usage metadata and relying on third-party network access. The risk is contextual: it contributes to a broad live-integration surface hidden behind a docs-oriented label.
curl -s https://api.heybossai.com/v1/models \
-H "Authorization: Bearer $SKILLBOSS_API_KEY"
This filtered model query is another authenticated external request. While routine, it still expands the live network surface of a skill that is described too narrowly, creating potential for unexpected data egress and trust confusion.
Filter by type:
curl -s "https://api.heybossai.com/v1/models?types=image" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY"
Fetching full docs for specific models involves external API interaction and may reveal model interests or planned usage. In isolation this is mild, but combined with the misleading skill identity it contributes to an under-disclosed third-party integration risk.
Get full docs for specific models:
curl -s "https://api.heybossai.com/v1/models?ids=mm/img,bedrock/claude-4-5-sonnet" \
-H "Authorization: Bearer $SKILLBOSS_API_KEY"
The chat completion example transmits message content to an external service and likely onward to downstream providers. This can expose sensitive prompts or conversational data, and the lack of strong warnings makes the risk more significant in this context.
curl -s -X POST https://api.heybossai.com/v1/chat/completions \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The media-generation sections add image, video, audio, and background-removal capabilities that are unrelated to a documentation expert role. This broadens the attack surface and increases the chance that user prompts, files, or URLs are sent to external services unexpectedly under a misleading skill identity.
This generation request sends prompt content to an external endpoint and may incur downstream provider processing. Because the skill is not transparently marketed as a generation/integration skill, the external transmission is more dangerous than a typical API example.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This generation request sends prompt content to an external endpoint and may incur downstream provider processing. Because the skill is not transparently marketed as a generation/integration skill, the external transmission is more dangerous than a typical API example.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This example both performs an external API call and fetches a returned URL to save content locally. That combines remote transmission with follow-on retrieval from a possibly different host, increasing risk of unexpected downloads, local file creation, and handling of untrusted remote content.
Save to file:
URL=$(curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "mm/img", "inputs": {"prompt": "A sunset over mountains"}}' \
The video generation request sends prompt data externally for processing. In this skill, such non-docs capability broadening makes the transmission more problematic because it may bypass user expectations about what the skill will do.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The video generation request sends prompt data externally for processing. In this skill, such non-docs capability broadening makes the transmission more problematic because it may bypass user expectations about what the skill will do.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The image-to-video example sends both prompt text and an image URL to an external service, which may expose sensitive media or internal resources referenced by URL. This is a meaningful data-egress concern, especially given the mismatch between declared purpose and actual behavior.
Image-to-video:
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The TTS request transmits user text to a remote provider chain for synthesis. Sensitive text may be exposed, and the transmission is insufficiently disclosed for a skill that users may assume is primarily informational/documentary.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The TTS request transmits user text to a remote provider chain for synthesis. Sensitive text may be exposed, and the transmission is insufficiently disclosed for a skill that users may assume is primarily informational/documentary.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
Uploading audio data to a remote endpoint can disclose confidential speech, biometrics, or personal information. The risk is elevated because the skill's framing does not prepare users for high-sensitivity media upload to third parties.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
Uploading audio data to a remote endpoint can disclose confidential speech, biometrics, or personal information. The risk is elevated because the skill's framing does not prepare users for high-sensitivity media upload to third parties.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The music-generation request sends user prompts externally and triggers creative model execution unrelated to documentation assistance. This broad capability increases data-sharing and cost exposure under a misleading trust boundary.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This image-processing call transmits image inputs or references to an external service. That may reveal sensitive visuals or accessible URLs, which is not clearly signposted by the skill's stated purpose.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
This image-processing call transmits image inputs or references to an external service. That may reveal sensitive visuals or accessible URLs, which is not clearly signposted by the skill's stated purpose.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
The document-processing example uploads or references documents for remote parsing/extraction, potentially exposing sensitive files and their contents to a third party. For a docs-related skill this might seem more contextually plausible, but the absence of privacy warnings still makes it dangerous.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
External web-search requests can disclose search intent and sensitive research topics to a third-party provider. Because this is part of a much broader hidden integration layer, users may not realize their queries are leaving the environment.
curl -s -X POST https://api.heybossai.com/v1/run \
-H "Authorization: Bearer $SKILLBOSS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
No suspicious patterns detected.