T01 · Skill Instruction Hijacking
- Location
SKILL.md:3- Finding
Mandatory API Routing and Proactive Tool Invocation Hijack Agent Behavior
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a legitimate video-analysis purpose, but it can proactively search a private video library and send sensitive queries or file paths to a configurable API endpoint without enough user control.
Install only if you trust the Searchables desktop app and want the agent to use your private video library. Before use, keep the API endpoint pinned to the expected local address or another trusted configured origin, do not let prompt text choose an arbitrary IP:port, and require explicit confirmation before searching private videos, processing local files, using browser-cookie-backed private content, or exporting anything to Notion.
SKILL.md:3Mandatory API Routing and Proactive Tool Invocation Hijack Agent Behavior
SKILL.md:34User-Controlled API Base URL Permits Server-Side Request Forgery
The activation text is overly broad, instructing the agent to use this skill whenever the user mentions generic video-related concepts. This can cause unnecessary invocation of a capability that accesses a local library and external API, increasing privacy risk and reducing user control over when sensitive video metadata or content is searched.
The instruction to always use this skill for any mention of YouTube, Bilibili, or generic video terms mandates automatic activation without meaningful exclusions. In context, this is more dangerous because the skill can inspect the user's local video library and interact with an external service, even when the user did not explicitly request that behavior.
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
cation required. Returns app, account, platform login, library, and credit state. Use this on first connection to guide user onboarding.
curl -s {baseUrl}/agent-api/setup/status
Response (fully set up):
{
"app": { "version": "1.5.0", "status": "running" },
"account": { "authenticated": true, "user": { "email": "user@example.com", "name": "User" } },
"platforms": {
"cookiesSource": "chrome",
"youtube": { "loggedIn": true },
"bilibili": { "loggedIn": false }
},
"library": { "videoCount": 1 },
"credits": { "balance": 517.7 }
}
Response (not logged in):
{
"app": { "version": "1.5.0", "status": "running" },
"account": { "authenticated": false, "user": null },
"platforms": {
"cookiesSource": null,
"youtube": { "loggedIn": false },
"bilibili": { "loggedIn": false }
},
"library": { "videoCount": 0 },
"credits": null
}
Search across all processed video c
The skill handles local video files and a semantically indexed local library but does not present a clear privacy notice before transmitting local file paths or content to the API. Users may not understand that sensitive local media and metadata could be processed or sent outside the immediate chat context.
The skill asserts that all video analysis must go through its API while later documenting a subtitle path that falls back to yt-dlp/platform retrieval. That inconsistency can mislead users and reviewers about what data paths are actually used, weakening informed consent and security review of external data access.
The skill's manifest centers on video search and analysis, but it also supports exporting derived content to Notion, an additional external transmission channel. This broadens data exposure beyond the stated purpose and can cause users to send summaries, transcripts, or notes to third-party services without clear scope limitation.
The skill recommends browser-cookie-based access to age-restricted and private content without an explicit privacy and security warning. Browser cookies are highly sensitive credentials; encouraging their use in this way increases risk of unauthorized access expectations, credential misuse concerns, and inadequate user consent.
The skill instructs the agent to send data via curl to a local API endpoint, which is an external transmission channel relative to the model/runtime. In context this is expected functionality, but it still creates a real data-flow boundary involving local library metadata, account status, and potentially video-derived content, so it should be treated as sensitive and consent-governed.
No authentication required.
curl -s {baseUrl}/agent-api/health
Response:
Several mandatory examples and required prompts are written as Chinese user-facing text, including the required confirmation wording and progress messages. The skill does not offer a language choice or state that Chinese is only an example, which may violate language/locale policy by implicitly forcing a specific language.
The proactive guidance tells the agent to consider searching the user's video library during unrelated questions, without explicit request or privacy warning. Because the library may contain private local videos and indexed transcripts, unsolicited inspection materially increases the chance of privacy violations and over-collection.
No suspicious patterns detected.