T09 · Insecure Skill Coding Practices
- Location
publish-manual.txt:23- Finding
Plaintext ClawHub Authentication Token Embedded in Documentation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is not a backdoor, but it exposes a ClawHub token and presents mock financial outputs as investment guidance while logging analyses locally.
Review carefully before installing. Do not rely on this skill for real investment decisions unless it is changed to use verified market data, clear timestamps, validated methods, and prominent financial-risk disclaimers. The exposed ClawHub token should be revoked, removed from all distributed copies, and audited. Users should also know that analysis requests may be saved locally in analysis_log.json.
publish-manual.txt:23Plaintext ClawHub Authentication Token Embedded in Documentation
analyzer.js:107Fabricated Market Data and Arbitrary Logic Presented as Actionable Investment Analysis
The declared description presents the skill as an AI-powered investment analysis assistant with analytical, advisory, forecasting, and optimization capabilities. However, the supplied code only implements an internationalization helper containing static translation dictionaries and simple functions for key translation and localized output formatting. It does not fetch market data, analyze assets, assess risk, generate recommendations from data, or optimize strategies. While the strings reference investment concepts, that is only UI/supporting text, not the substantive behavior described. Therefore, the code chunk’s actual purpose is materially different from the declared purpose.
The manual embeds a live-looking ClawHub login token and explicitly instructs operators to use it to authenticate. Exposed credentials are a direct secret-disclosure issue and are unrelated to the investment-analysis function of the skill, which makes this especially suspicious and dangerous because anyone reading or indexing the file could reuse the token for unauthorized account access or publishing actions.
This markdown file uses Chinese for all substantive feature descriptions, which imposes a specific language on users without any opt-in or explanation. Under the language/locale policy rule, this is a natural-language policy concern because the file does not indicate that the skill is region-specific or provide an alternative language option.
This markdown file contains user-facing instructions and promotional content exclusively in Chinese, and there is no indication that the skill is region-specific or that users can choose another language. That can violate language/locale policy when a skill imposes a language without explicit opt-in or justification.
The README presents the skill as providing investment analysis, market prediction, and portfolio optimization without any visible disclaimer about financial risk, uncertainty, or that outputs should not be treated as definitive investment advice. In a finance-focused skill, this omission can mislead users into over-trusting model outputs for real-money decisions, increasing the chance of harmful financial losses or inappropriate reliance.
The skill explicitly offers investment analysis, forecasts, and recommendations but provides no disclaimer that outputs are informational only and may be inaccurate, incomplete, or unsuitable for a user's financial situation. In a finance context, users may over-rely on the tool's outputs and make harmful financial decisions, especially because the description uses authoritative language such as risk assessment, optimization, and AI prediction.
The manifest description is written entirely in Chinese and presents the skill as a Chinese-language assistant, but there is no indication that users can choose another language or that the skill is intentionally limited to a Chinese-speaking region. This creates a natural-language locale policy concern because the skill appears to impose a specific language without opt-in or justification.
The file's human-readable comments are entirely in Chinese, which imposes a specific language on maintainers or users reading the skill source. There is no indication that this language choice is optional, configurable, or justified by a region-specific requirement, which matches the locale-policy concern for natural-language content.
The JSON values for trend, risk level, recommendation, and ROI are written in Chinese, indicating a fixed language choice in the skill output. There is no evidence in this file of user language selection or a documented reason for enforcing that locale, which creates a natural-language policy concern.
The skill advertises real-time investment analysis, but the implementation uses hardcoded mock prices and fabricated trend/ROI outputs. In an investment-advice context, this can mislead users into making financial decisions based on false or stale information, which is materially dangerous even without code execution or classic injection.
The comment claims the function obtains real-time financial data, but the code actually returns mock data. This mismatch increases the risk of developer or user trust in nonexistent live-data behavior, causing deceptive outputs in a high-stakes financial domain.
Natural-language strings throughout the skill, including comments, console output, and CLI usage text, are exclusively in Chinese. This effectively forces a specific language without any user opt-in or documented region-specific justification, which matches the language/locale policy violation criteria.
The skill writes user-provided investment analysis history to disk without notice or consent. Investment interests and portfolio-related inputs can be sensitive financial profiling data, so undisclosed persistence creates privacy risk and potential exposure to other local users or processes.
The file uses Chinese field names and descriptions throughout, including usage examples and recommendations, which effectively forces a specific language for users of the skill. The policy allows fixed locale only when the constraint is explicitly documented and justified, but this JSON provides no opt-in or stated region-specific limitation.
The skill metadata presents the skill name, description, and authoring context entirely in Chinese, with no indication that users can select another language or that the skill is intended only for a Chinese-language audience. Under the policy, forcing a language or locale without opt-in or clear regional justification is a natural-language policy concern.
SQP-3 applies to all file types and covers natural-language policy violations such as forcing a specific language without user opt-in. This publication guide presents all instructions in Chinese and does not indicate that users may choose another language or that the skill is limited to a Chinese-speaking region.
The manifest focuses on analysis, risk assessment, and investment strategy advice, but the implementation also persists every analysis result to a local JSON log file. Persistent storage is not necessarily implied by the stated purpose and represents behavior beyond the described assistant functionality.