T07 · Tool Hijacking and Spoofing
- Location
SKILL.md:40- Finding
Execution of Unverified External Binaries and Scripts
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Windows memory-cleaning skill is mostly disclosed, but it asks the agent to run unverified local programs, terminate processes, and delegate disk cleanup in ways that need human review before installation.
Install only if you trust the local aioom and storage-clean files at the hardcoded Windows paths. Before allowing cleanup, use dry-run or preview output, verify exact process IDs and file paths, and avoid running this with administrator privileges unless you intentionally want system-wide process and filesystem authority.
SKILL.md:40Execution of Unverified External Binaries and Scripts
SKILL.md:127Overbroad Process Termination Based on Command-Line Substring
The manifest advertises process killing and, in the documentation, disk-cleaning behavior without an upfront warning about service interruption, unsaved work loss, or file deletion risk. In an agent setting, that omission can cause users to authorize dangerous actions without informed consent, increasing the chance of accidental disruption or data loss.
The trigger list in the manifest is entirely in Chinese, and the operational examples throughout the document assume Chinese-language user requests. This appears to impose a language-specific interaction model without opt-in or an explicit justification that the skill is intended only for a Chinese-speaking locale.
The skill is presented as a Windows memory-management tool, but it also invokes a separate storage-cleaning skill to scan disks and delete files. This broadens the skill’s effective privilege and capability beyond its declared purpose, creating a scope mismatch that can mislead users or orchestrators into authorizing destructive filesystem actions they did not expect.
Disk and storage cleanup are destructive capabilities unrelated to the stated role of a memory guardian. Because the skill can pass arbitrary paths into an external cleaner, a user invoking a memory-related assistant action could be steered into file deletion or recycling workflows outside the expected trust boundary.