T09 · Insecure Skill Coding Practices
- Location
SKILL.md:10- Finding
Credentials and Long-Lived Bearer Tokens Are Sent to an Unrestricted API Origin
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly aligned with a collections platform, but it handles credentials, long-lived tokens, and outbound debtor communications with under-specified safeguards.
Install only in an environment where FIBEK_BASE_URL is pinned to the legitimate HTTPS Fibek API and network egress is restricted. Treat the skill as handling sensitive financial and contact data; require users to review recipients, channels, and campaign audiences before any message or campaign is sent, and ensure bearer tokens are stored and cleared securely.
SKILL.md:10Credentials and Long-Lived Bearer Tokens Are Sent to an Unrestricted API Origin
SKILL.md:113Swagger Discovery Permits Arbitrary Server-Side URL Requests
The instructions mandate a Spanish greeting and conversation flow, and later formatting rules also require Spanish status/date rendering. There is no opt-in or documented justification that this skill is intentionally limited to Spanish-speaking users, which creates a language-policy concern.
The skill enables sending payment reminders and account statements over external channels like email and WhatsApp without requiring an explicit user confirmation or warning about outbound disclosure. In a collections context, this can lead to unintended transmission of sensitive financial information to the wrong recipient or via an unintended channel, especially when contact selection is optional or ambiguous.
The documented campaign validation and execution flows describe outbound campaign capabilities without any warning, approval gate, audience preview, or rate/impact constraints. In this business collections setting, a mistaken or overly broad execution could trigger mass debtor communications, causing privacy issues, reputational harm, and potentially unauthorized bulk outreach.
These instructions require Spanish translations and Spanish-formatted dates/status text for all responses, indicating a fixed locale. Without a user language choice or a documented locale-specific justification, this is a natural-language policy violation.