T09 · Insecure Skill Coding Practices
- Location
SKILL.md:38- Finding
Hardcoded Token Exposed in an Untrusted External Subscription Endpoint
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a Markdown guide, but it repeatedly embeds an unrelated token-bearing external endpoint and broad triggers, so users should review it carefully before installing.
Install only after removing or validating the repeated endpoint and token-like value, narrowing the triggers to the actual AI-security learning topic, and confirming the merged sections are intentional. The artifact does not show automatic execution or persistence, but the unexplained external subscription URL is not appropriate for a general guide.
SKILL.md:38Hardcoded Token Exposed in an Untrusted External Subscription Endpoint
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The single-word trigger "xn" is extremely vague and is likely to collide with unrelated text, abbreviations, or tokens. In a skill already containing suspicious URL and token content, such a broad trigger can lead to accidental activation and propagation of untrusted endpoint data into unrelated interactions.
This repeated trigger block again uses the single-word activation "xn," compounding the accidental invocation risk across duplicated sections. Duplication makes the unsafe trigger harder to audit and increases the chance that at least one copy survives future edits or automated merges.
Another duplicated section retains the ambiguous "xn" trigger, showing that unsafe activation logic has propagated through merges. Repetition increases operational risk because multiple blocks may be parsed differently by tooling, making unintended activation more likely.
The final repeated occurrence of the "xn" trigger confirms a pattern of unsafe, overly generic invocation criteria embedded throughout the file. Given the surrounding endpoint-centric content, this creates a realistic pathway for broad accidental activation and exposure of suspicious external references.
The file presents itself as an AI-security learning guide, but later merged sections redefine the skill around a subscribe endpoint and token-like artifacts. This semantic mismatch is dangerous because it can mislead users or agents into trusting and surfacing unrelated external indicators, URLs, or secrets under the guise of benign educational content.
The trigger conditions include broad phrases like general AI-security help requests, which can cause the skill to activate in many unrelated contexts. Because the skill content contains suspicious merged endpoint and token material, overbroad triggering raises the chance that untrusted or irrelevant content is injected into normal conversations.
This section stores and promotes a subscription API URL with a token-like query parameter inside a skill advertised as an AI-security learning resource. Embedding such artifacts can expose credentials, trigger unsafe agent behavior, or repurpose the skill into a delivery mechanism for untrusted external infrastructure.
Repeated subsections for the same skill name overwrite the original educational framing with a concrete subscribe endpoint, making the skill's effective behavior and intent ambiguous. This increases the chance that downstream systems index, trigger, or summarize the maliciously or accidentally injected endpoint content instead of the declared topic.