ClawHub
Back to skill

Security audit

AtroSnow File Management

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only skill for an application file-management workflow, with no hidden execution behavior, but it has one inconsistent workflow instruction users should correct before relying on it.

Before installing or using this skill, treat it as project documentation and fix the final workflow so business saves use createFileMedia() in the service layer. Also avoid uploading sensitive files unless the application is intended to store them temporarily and possibly promote them to permanent records.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill explicitly says earlier that business services should use IFileMediaService.createFileMedia() and that /filemedia/b/saveFileMediaFile is only for the file-management module itself, but the final '完整开发流程' then instructs developers to use saveFileMediaFile during normal business saves. This inconsistency can cause developers to implement the wrong persistence path, bypass expected service-layer controls/callback association logic, and create broken or unsafe file-handling behavior in production.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
81% confidence
Finding

This markdown file documents safety-relevant behaviors including file upload, temporary caching, download, and formal persistence of files, but it does not warn users that files may be stored on the server, retained temporarily, or converted into permanent records. For markdown files, SQP-2 applies when descriptions omit warnings about behaviors that could affect user data, privacy, or system integrity.

Content

No source excerpt is available for this finding.