T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Unpinned Package Installation and Persistent Third-Party Registry Configuration
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This China-cloud deployment guide is mostly purpose-aligned, but some default examples can expose cloud services or persistently change developer tooling without enough warning or scoping.
Review and adapt the commands before use. Treat the public endpoint and public bucket examples as intentionally public-only patterns, add authentication or gateway controls for APIs, use dedicated empty buckets for static assets, scan build output for secrets, and avoid persistent global registry changes unless you understand and can reverse them.
SKILL.md:18Unpinned Package Installation and Persistent Third-Party Registry Configuration
SKILL.md:59Public Unauthenticated Serverless Endpoints Enabled by Default
SKILL.md:120Bucket-Wide Public Read Access Applied Without Content Validation
The instruction frames the skill as an expert specifically for deployment to Chinese cloud platforms and repeatedly centers China-specific operational assumptions, but it does not explicitly offer the user a language or locale choice. Under the policy, forcing a locale-specific mode without opt-in can be a natural-language policy violation unless clearly documented as a justified region-specific tool.
The skill instructs users to set an OSS bucket ACL to public-read for static hosting, but it does not explicitly warn that all uploaded objects may become publicly accessible. In a deployment-focused skill, this omission can lead users to unintentionally expose sensitive build artifacts, backups, config files, or misuploaded secrets.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Check if domain has ICP filing
curl -s "https://hlwicpfwc.miit.gov.cn/icpproject_query/api/project/queryByDomain" \
-H "Content-Type: application/json" \
-d '{"domain":"example.com"}'