figma
3 findings (2 critical, 1 info), mainly command injection, policy violation. Most recent scan 2026-10-22.
Second scanner: NVIDIA SkillSpector
Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
Bring Figma into a HyperFrames video - rendered assets, brand tokens, components, storyboard frames as reconstructed motion (frames read as states, not slides), shaders and connector-assisted motion. Use when the person pastes a figma.com link or asks to use a Figma design, frame, logo or brand.
- Package
- 2 files, 11 KB
- SKILL.md
- 882 words, 6 sections
- Code
- JavaScript (1)
SKILL.md covers: Figma → HyperFrames · Access · Commands · Motion (connector) · Shaders · Storyboards: frames are KEYFRAMES, not slides
Findings
CRITICAL Node.js child_process module usage for shell command execution Command Injectionstatic
Pattern detected: from "node:child_process"
scripts/verify-motion.mjs:24
import { execFileSync, spawnSync } from "node:child_process";CRITICAL Node.js child_process module usage for shell command execution Command Injectionstatic
Pattern detected: spawnSync(
scripts/verify-motion.mjs:113
const r = spawnSync("ffmpeg", ["-i", a, "-i", b, "-lavfi", "psnr", "-f", "null", "-"], {INFO Skill does not specify a license Policy Violationstatic
Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.
SKILL.md
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 6.0 KB |
scripts/verify-motion.mjs | script | 4.9 KB |
Environment variables referenced
BAD_TOKEN FIGMA_TOKEN
Package contents recorded 2026-10-22 at commit 4371981b740d. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Bytecode analyzer.
- Pipeline analyzer.
- Correlation analyzer.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/heygen-com/hyperframes
- Raw scan result: heygen-com-hyperframes-skills-figma-scan.json
- Badge for your README:
 - Request a re-scan