T09 · Insecure Skill Coding Practices
- Location
lib/run-manifest.cjs:12- Finding
Path Traversal Through Unsanitized Run Identifier
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill has a coherent Figma visual comparison purpose, but it needs review because it runs broad local automation with weak containment and mutable setup steps.
Install only if you are comfortable running it in an isolated workspace or container, with a read-only/minimum-scope Figma token and only trusted page URLs. Pin dependencies yourself before setup, avoid running install commands as root, and do not share or commit figma-pixel-runs artifacts without reviewing them for sensitive screenshots or Figma data.
lib/run-manifest.cjs:12Path Traversal Through Unsanitized Run Identifier
lib/page-render.cjs:102Unrestricted Page Rendering in Chromium With Browser Sandbox Disabled
SKILL.md:44Unpinned Host-Level Dependencies and Ambiguous npx Execution
Referenced artifact was not completely inspected
Use `scripts/run-pipeline.cjs` as the primary orchestration entry point.
Referenced artifact was not completely inspected
Use `scripts/run-pipeline.cjs` as the primary orchestration entry point.
Referenced artifact was not completely inspected
Use `scripts/run-pipeline.cjs` as the primary orchestration entry point.
Referenced artifact was not completely inspected
Use `scripts/run-pipeline.cjs` as the primary orchestration entry point.
Referenced artifact was not completely inspected
Use `scripts/run-pipeline.cjs` as the primary orchestration entry point.
Referenced artifact was not completely inspected
Use `scripts/run-pipeline.cjs` as the primary orchestration entry point.
Referenced artifact was not completely inspected
Use `scripts/run-pipeline.cjs` as the primary orchestration entry point.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
if (!token) {
throw new Error(
'FIGMA_TOKEN is required. Create a Figma personal access token and pass it via environment variable.'
);
}
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
if (!token) {
throw new Error(
'FIGMA_TOKEN is required. Create a Figma personal access token and pass it via environment variable.'
);
}
The skill uses 'network' capability that is not listed in its permissions. This may indicate deceptive intent or missing permission declarations.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
The required network flow is:
- read `FIGMA_TOKEN` in `lib/config.cjs`
- call `https://api.figma.com/v1/files/...`
- call `https://api.figma.com/v1/images/...`
- download the Figma-generated reference image for visual comparison without sending the token to that image URL
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
The required network flow is:
- read `FIGMA_TOKEN` in `lib/config.cjs`
- call `https://api.figma.com/v1/files/...`
- call `https://api.figma.com/v1/images/...`
- download the Figma-generated reference image for visual comparison without sending the token to that image URL
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
The required network flow is:
- read `FIGMA_TOKEN` in `lib/config.cjs`
- call `https://api.figma.com/v1/files/...`
- call `https://api.figma.com/v1/images/...`
- download the Figma-generated reference image for visual comparison without sending the token to that image URL
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
The required network flow is:
- read `FIGMA_TOKEN` in `lib/config.cjs`
- call `https://api.figma.com/v1/files/...`
- call `https://api.figma.com/v1/images/...`
- download the Figma-generated reference image for visual comparison without sending the token to that image URL
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.
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.
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.
Without these packages, system libraries, and a working browser executable, the skill will not work fully.
Rendering, image diffing, or diff-region analysis may fail immediately depending on what is missing.
How to create a Figma token:
- https://help.figma.com/hc/en-us/articles/8085703771159-Manage-personal-access-tokens
Main packages used by the skill:
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.
Copy this skill into your global skills directory:
mkdir -p ~/.claude/skills/figma-pixel
cp -r . ~/.claude/skills/figma-pixel/
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.
Or for a specific project:
mkdir -p .claude/skills/figma-pixel
cp -r . .claude/skills/figma-pixel/
The skill description broadens from visual QA/reporting into directly editing implementation code and adding project assets. That expansion increases the blast radius of a skill invoked for comparison work, because it can modify application code and static resources in response to external Figma content and browser-rendered observations.
The invocation terms are broad enough to match many common UI requests, which can cause this high-privilege skill to activate in situations where the user did not specifically intend browser automation, external API access, or code modification. In context, the skill has Bash, Write, Edit, and network-capable browser behavior, so overbroad routing increases the chance of unintended sensitive actions.
The skill states that it should 'never create working folders, scratch files, or runtime artifacts inside the implementation project directory' and that all run outputs go under the skill-owned figma-pixel-runs directory. Later, L110 instructs saving exported child-node PNGs to the implementation project's public/static directory, which contradicts the earlier prohibition against placing generated artifacts in the project tree.
The skill instructs use of npx playwright without pinning an exact package version, which can fetch whatever version is current at execution time. In a security-sensitive workflow that loads pages and browser tooling, this creates supply-chain and reproducibility risk because behavior and transitive code can change unexpectedly.