Back to skill

Security audit

project-init

Security checks for vulnerabilities and agentic risk

Overview

The scanners rate this skill suspicious because its broad “Rust” trigger may start a project setup workflow for unrelated Rust questions; the review is incomplete because some referenced files were not found in the scanned bundle.

Review the trigger scope and identify the missing initialization script before installing, since the scan could not inspect it. If you proceed, consider whether the broad trigger could cause setup actions during unrelated Rust questions.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • 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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

The trigger list splits a project-creation phrase into separate entries, including the overly broad trigger “Rust.”

Medium
Category
Trigger Abuse
Confidence
99% confidence
Finding

The standalone trigger “Rust” can activate this project-initialization workflow for unrelated Rust questions rather than explicit scaffolding requests. If triggers control automatic invocation, this could cause unintended file creation or execution of initialization and verification commands; the overwrite-confirmation requirement reduces potential damage but does not prevent inappropriate activation.

Content

No source excerpt is available for this finding.