T09 · Insecure Skill Coding Practices
- Location
SKILL.md:28- Finding
Bearer Credential Disclosure Through an Unrestricted API Base URL
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is coherent for AlphaGBM macro tracking, but it deserves review because it uses sensitive portfolio-linked analysis, an API key, broad triggers, and an overrideable API destination.
Install only if you are comfortable connecting this agent to AlphaGBM with an API key and having macro analysis tied to your portfolio or profile data. Use a tightly scoped key, keep ALPHAGBM_BASE_URL pointed only at the official service, and confirm add/remove actions or portfolio-linked lookups when the prompt is ambiguous.
SKILL.md:28Bearer Credential Disclosure Through an Unrestricted API Base URL
SKILL.md:143Untrusted Remote Impact Analysis Is Presented Without Prompt-Injection Controls
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
DELETE /api/research/macro/<INDICATOR_KEY>
Uses the key (VIX, not an id). 404 if not tracked.
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
→ Present each indicator: value, change, impact on their holdings
3. User: "Stop tracking DXY"
→ DELETE /api/research/macro/DXY
4. User: "Is high VIX hurting my positions?"
→ GET /api/research/macro → read VIX's impact_analysis field
The skill advertises AI-generated impact analysis tied to the user's holdings but does not clearly warn users that portfolio-related data may be transmitted to an external AlphaGBM service. This creates a transparency and privacy problem: users may unknowingly authorize disclosure of sensitive holdings information to a third party.
The trigger guidance is broad enough to activate on generic finance terms like "macro", "yield", "VIX", and Chinese equivalents, which can cause the skill to run when the user did not clearly intend to use this external macro-tracking service. In this skill, unintended invocation is more concerning because the workflow includes portfolio-linked impact analysis and external API use, increasing the chance of surprise data processing or unintended state changes.