Back to skill

Security audit

Excalidraw Tech Illustration

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent diagram generator, but it asks agents to run an unpinned third-party npx package and to automatically modify project files.

Install only if you are comfortable with the agent creating and moving diagram files in your repository. Pin or preinstall a reviewed Excalidraw CLI version before use, and review any index.json or README changes before committing.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:101
Finding

Unpinned Third-Party Package Execution via npx

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 101
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: Medium

Complete Code Snippet:

bash
npx @swiftlysingh/excalidraw-cli convert input.excalidraw output.png --format png --output output.png

Technical Analysis

The documented rendering command invokes @swiftlysingh/excalidraw-cli through npx without specifying a reviewed package version or integrity constraint. If the package is not already available locally, npx may retrieve and execute the version currently resolved by the npm registry.

Consequently, the code executed during rendering can change after the Skill has been reviewed. A compromised maintainer account, malicious package release, registry compromise, or unexpected upstream update could introduce arbitrary behavior. No evidence shows that the named package is currently malicious; the finding concerns the unsafe, unpinned execution mechanism.

Attack Path

  1. An attacker compromises the package, its publisher account, or the applicable package-distribution path.
  2. The attacker publishes a malicious version under the same package name.
  3. A user or Agent follows the command in SKILL.md.
  4. npx resolves and downloads the unpinned package version.
  5. Package lifecycle logic or the invoked CLI executes with the permissions and environment of the Agent process.
  6. The malicious code can access resources available to that process.

Impact Assessment

Successful exploitation could permit arbitrary code execution with the invoking Agent's privileges. Depending on its runtime permissions, the malicious dependency could read or modify accessible project files, inspect environment variables and credentials, make outbound network requests, or alter generated artifacts. The scope is limited by the operating-system account, sandbox, filesystem permissions, and network restrictions applied to the proc ...[truncated 4 chars]

Remediation
View remediation

Remediation Suggestions

  1. Pin the CLI to an explicitly reviewed version, for example:
    bash
    npx --yes @swiftlysingh/excalidraw-cli@<reviewed-version> convert input.excalidraw output.png --format png --output output.png
    
  2. Prefer declaring the package in a project manifest and committing a lockfile that records exact transitive dependency versions and integrity hashes.
  3. Install dependencies with a lockfile-enforcing command such as npm ci, then invoke the local binary rather than allowing on-demand resolution.
  4. Use the official npm registry explicitly and enforce package provenance or signature verification where supported.
  5. Review the selected package version and its dependency tree before approval.
  6. Run rendering in a restricted environment with minimal filesystem access, no unnecessary credentials, and limited outbound network connectivity.
  7. Configure automated dependency monitoring and require security review before changing the pinned version.
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Vague Triggers

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger phrases are broad and map to very common user intents such as generating diagrams, flowcharts, or technical illustrations, making accidental or unnecessary activation likely. In context, activation can cause file creation, file moves, rendering commands, and project index modifications, so overbroad matching expands the chance of unintended side effects beyond what the user explicitly requested.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The skill metadata and trigger phrases are entirely specified in Chinese and imply a fixed-language invocation model, with no indication that users may choose another language or locale. This can violate language-choice policy when a skill enforces a specific language without opt-in or justification.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
93% confidence
Finding

The skill instructs use of npx @swiftlysingh/excalidraw-cli without pinning an exact package version or integrity source, which creates a supply-chain risk at execution time. A future compromised or breaking package release could be fetched and run automatically, and because npx executes code from the package, this can lead to arbitrary code execution in the agent environment.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill mandates moving generated files into repository directories and updating index.json and statistics, but provides no requirement for user confirmation or safeguards around modifying existing project content. This is dangerous because merely invoking the skill can mutate tracked files and metadata, causing unintended repository changes, overwrite risk, and persistence of agent-produced artifacts in the project.

Content

No source excerpt is available for this finding.