T09 · Insecure Skill Coding Practices
- Location
SKILL.md:38- Finding
Externally Exposed WebSocket Service Without Documented Authentication or Transport Security
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a legitimate communication purpose, but its examples encourage broad network exposure and automatic file transfer behavior without enough access-control guidance.
Review before installing or using in shared networks. Bind servers to localhost unless you explicitly need remote access, add authentication and TLS, restrict allowed senders, avoid broad auto-download listeners, quarantine and validate received files, and be deliberate about any local files or folders sent to Aliyun OSS.
SKILL.md:38Externally Exposed WebSocket Service Without Documented Authentication or Transport Security
SKILL.md:145Automatic Persistence of Remotely Supplied Files Without Documented Validation
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
File transfers use Aliyun OSS. Set these environment variables:
# .env file
OSS_ENDPOINT=your-oss-endpoint
OSS_BUCKET_NAME=your-bucket-name
OSS_ACCESS_KEY_ID=your-access-key
The documented listener behavior shows automatic downloading of remote file content into a local directory, but it does not clearly warn that untrusted remote content will be written to the filesystem. This increases the risk of users enabling auto-downloads without considering disk-write side effects, malware staging, or unsafe handling of attacker-controlled filenames/content.
The skill explicitly states that sending files, images, and folders will automatically upload local content to Aliyun OSS, but it does not prominently warn that local data is being transmitted to a third-party remote service. In an agent setting, this can lead to unintended exfiltration of sensitive local files or directories if a caller assumes these are local-only transfers.
The skill documents default client ID generation using the device MAC address plus a UUID suffix, which exposes a persistent hardware-derived identifier without explicit user consent. This can enable cross-session tracking, device correlation, and disclosure of sensitive host identity information in environments where anonymity or privacy is expected.
No suspicious patterns detected.