Back to skill

Security audit

Print Failure Analyst

Security checks for vulnerabilities and agentic risk

Overview

This skill appears benign: it diagnoses 3D printing failures and uses a disclosed local failure log/report workflow aligned with that purpose.

Installers should know that using the log/report features will store troubleshooting details locally, including any sensitive information they type into descriptions or notes. Avoid putting private customer, business, or location details in the log, and choose report output paths carefully to avoid overwriting unrelated files.

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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill explicitly maintains a personal failure log in assets/failure-log.json and can save generated reports to arbitrary files, but the description does not warn users that their printer, material, descriptions, notes, and possibly free-form troubleshooting details may be persisted. This can cause unintentional retention of personal or sensitive operational data, especially because users may not realize that routine diagnostic interactions can be logged or written to disk.

Content

No source excerpt is available for this finding.