T08 · Insecure Dependencies
- Location
README.md:10- Finding
Unpinned Third-Party Installer and Mutable Skill Source
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent AI logo generator, but it needs Review because it can automatically use a stored login token, spend service credits, send logo prompts to a third-party API, and save downloaded files with weak scoping and login hardening.
Install only if you are comfortable sending logo prompts and brand details to ailogogenerator.online, storing a local bearer token, and spending service credits. Prefer explicit invocation, confirm before generation/download, keep auth.json protected, delete it to log out, and review the generated download URL/path before saving files.
README.md:10Unpinned Third-Party Installer and Mutable Skill Source
login.mjs:18OAuth Callback Accepts Uncorrelated Bearer Tokens
login.mjs:71Reflected HTML Injection in Login Callback Page
You're now authenticated${email ? ` as ${email}` : ""}.
You can close this tab and return to your terminal.
Token saved to ~/.config/ailogogenerator.online/auth.json
skill.md:108Unvalidated Server-Provided Image Download URL
Referenced artifact was not completely inspected
Replace `<SKILL_DIRECTORY>` with the actual directory where this `skill.md` lives. You can find it by checking `$CLAUDE_SKILL_DIR` or resolving the path relativ
Referenced artifact was not completely inspected
oken expired. Delete `~/.config/ailogogenerator.online/auth.json`, then re-run `login.mjs` to get a fresh token. Then retry the generation automatically.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
npx skills add qq919006380/ai-logo-generator
That's it. Claude Code picks up skills from `~/.claude/skills/` automatically.
---
The conversational example says the skill may load automatically for a broad request like creating an icon or logo, which encourages implicit invocation without a clearly bounded trigger. Because this skill performs browser auth, network requests, token use, and file writes, overly broad activation increases the chance of unintended side effects from normal conversation.
The README describes opening a browser for authentication, storing a token at a fixed local path, sending prompt data to a remote API, polling the service, downloading a generated file, and writing it locally, but does not present a prominent warning about these privacy and side-effect implications. Users may disclose sensitive branding or project information, persist credentials on disk, and create local files without fully informed consent.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The README explicitly says the skill can be triggered by ordinary conversational requests such as asking to make a logo, even without a slash command. Overly broad auto-trigger guidance can cause the agent to invoke the skill in contexts the user did not clearly intend, increasing the chance of unexpected browser launches, network requests, authentication flows, or file writes.
The README states that an authentication token is stored at ~/.config/ailogogenerator.online/auth.json but does not warn users about local credential storage, file permissions, or the consequences of token theft. If that file is readable by other local users, synced to backups, or exposed through logs or tooling, an attacker could reuse the token to access the associated account.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
---
name: ai-logo-generator
version: 1.0.0
description: "Generate professional AI logos using ailogogenerator.online. Use this skill whenever the user wants to create a logo, brand icon, app icon, favicon, or any visual identity asset — even if they don't explicitly mention 'logo generator'. Covers requests like 'make me a logo', 'design an icon for my app', 'I need a brand mark', or 'generate a logo for my startup'."
license: MIT-0
---
The skill description is overly broad and instructs activation for almost any visual identity request, including generic icon and design tasks. This can cause the agent to invoke an external stateful service unexpectedly, exposing user prompts to a third party and potentially initiating credit-consuming operations outside a clearly bounded logo-only workflow.
The invocation guidance says to use the skill for any logo, icon, or brand identity generation request without defining boundaries or disallowed cases. In context, that ambiguity increases the chance of unintended tool use, third-party data disclosure, and paid API calls based on normal conversational design requests rather than explicit consent.
The skill directs the agent to download the generated image and save it into the current working directory automatically, but it does not require notifying the user beforehand or obtaining consent for local file creation. Automatic filesystem writes can surprise users, overwrite nearby workflow expectations, and create unwanted artifacts on the host environment, especially when triggered from a broadly activated skill.
The workflow states that the skill downloads imageUrl and saves the result to ./logo-*.png, but the description does not clearly warn that files will be written into the current working directory. Although the example shows a saved path, it lacks an explicit caution about local file creation and potential overwrites or workspace effects.
Detected: suspicious.dangerous_exec