T09 · Insecure Skill Coding Practices
- Location
SKILL.md:93- Finding
Published Default Login Credentials
- Content
View full analysis
- Remediation
View remediation
` that cannot function as a real credential. ]]>
Security audit
Security checks for vulnerabilities and agentic risk
This is mostly a Data Mini support FAQ, but it publishes fixed login credentials and insecure copyable authentication examples that should be reviewed before use.
Review this skill before installing or sharing it. Remove or replace the fixed default credentials with secure onboarding instructions, rotate any matching deployed account, and update the crypto/auth examples to use environment-specific secrets, stronger algorithms where compatible, and no logging of authentication material.
SKILL.md:93Published Default Login Credentials
SKILL.md:562Weak Hardcoded HMAC Key and Authentication Material Logging
The skill discloses a default username and password in plain text, which can directly enable unauthorized access if those credentials are still valid in any deployment. In a FAQ/help skill, this is especially dangerous because it operationalizes access rather than merely describing concepts, making accidental or abusive reuse much more likely.
Exposing default login credentials without warning normalizes insecure practices and may lead users to attempt shared or unchanged factory credentials in real environments. Because this is customer-facing operational guidance, the context makes it more dangerous: it encourages direct use of credentials in environments that may contain sensitive business or healthcare-related data.
The file plainly discloses and operationalizes a username and password, which is a direct secret exposure issue. Even if intended for setup convenience, publishing credentials in reusable documentation creates a durable compromise path and can result in credential stuffing, unauthorized access, or copy-forward into other environments.
The trigger description includes generic phrases such as “怎么使用XX功能”, “为什么报错XX”, and “如何配置XX”, which overlap with ordinary support questions and could match many unrelated conversations. The file does not provide limiting context, exclusion conditions, or negative examples to clarify when this skill should activate versus when another skill should handle the request.
The skill goes beyond answering FAQs and provides extensive executable Java/JavaScript workflow scripting examples, including code that manipulates runtime context, mock data, HTTP flows, and cryptographic routines. This expands the skill from informational support into code-generation and operational automation, increasing the chance that users deploy unsafe, overprivileged, or unreviewed scripts into production workflows.
No suspicious patterns detected.