Security audit

Exfat Recovery

Security checks for vulnerabilities and agentic risk

Overview

This skill is coherent as an exFAT recovery guide, but it includes high-impact raw disk writes and persistent SYSTEM-level Windows automation without enough safeguards.

Review carefully before installing or following this skill. Treat the recovery sections as potentially destructive: make a full disk image first, independently verify the drive number, serial/model, partition offset, filesystem type, and backup size, and avoid the persistent SYSTEM scheduled task or shutdown hook unless it is moved to an administrator-protected location with documented removal steps.

A.I.G

Vulnerability Patterns

System PersistenceInstalls backdoors, hooks, services, or scheduled tasks that survive the run
Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
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

Findings (3)

T06 · System Persistence

Error

Location: references/prevention-scripts.md:78
Finding: Highest-Privilege Scheduled Task Executes a User-Writable Script
Content: View full analysis
\backups`, which is ordinarily writable by that user. This creates an unsafe trust boundary: a machine-level privileged execution mechanism relies on code controlled by a less-privileged account. If that account or any process running under it can replace or modify `backup_boot_region.ps1`, the scheduled task will execute the modified content as `SYSTEM`. The weekly trigger and `StartWhenAvailable` setting provide durable execution across reboots and missed schedules. Hidden execution and execution-policy bypass reduce visibility and remove controls that might otherwise prevent an untrusted script from running. ### Attack Path 1. An administrator follows the documented setup and registers `BackupExFATBootRegion`. 2. The task is config ...[truncated 1145 chars]
Remediation: View remediation

T06 · System Persistence

Error

Location: references/prevention-scripts.md:21
Finding: Machine Shutdown Hook References a User-Modifiable PowerShell Script
Content: View full analysis
\backups`, where the corresponding non-adminis ...[truncated 1644 chars]
Remediation: View remediation

T09 · Insecure Skill Coding Practices

Error

Location: SKILL.md:112
Finding: Unvalidated Raw-Disk Restore Can Overwrite the Wrong Physical Device
Content: View full analysis
Remediation: View remediation

SkillSpector

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 (2)

Missing User Warnings

High

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The skill includes raw disk write instructions that can overwrite bytes directly on a physical drive using a user-supplied device path and partition offset, but it does not prominently warn that a wrong PhysicalDrive number, incorrect offset, or stale backup file can irreversibly corrupt the wrong disk or destroy partition/filesystem metadata. In a recovery skill, users are likely to run high-risk commands while stressed and may copy them with minimal validation, which makes omission of explicit safety checks and warnings materially dangerous.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The file instructs users to make persistent privileged system changes by registering a shutdown script via Group Policy registry keys and creating a scheduled task that runs as SYSTEM with ExecutionPolicy Bypass. In a recovery skill this is likely intended as automation, but presenting these steps without prominent warnings, least-privilege guidance, validation of drive identifiers, or rollback instructions increases the chance of misuse, persistence abuse, or system instability.
Content: No source excerpt is available for this finding.