Security audit

Zustand State

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only Zustand state-management skill with expected examples and no evidence of hidden execution, data exfiltration, or agent persistence.

Safe to install for Zustand help. When using its persist examples, only persist explicit non-sensitive state and avoid storing secrets, auth tokens, or sensitive personal data in browser or device storage.

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
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (5)

Vague Triggers

Medium

Confidence: 96% confidence
Finding: The description says the skill triggers on generic terms like "zustand" and broad API names such as "persist" and "devtools". Without negative examples or context constraints, these common terms could match unrelated discussions and cause unintended invocation.

Missing User Warnings

Medium

Confidence: 87% confidence
Finding: This markdown file documents persistence middleware that writes state into localStorage, and the examples show data being stored without any disclosure about privacy, sensitivity, or device-level persistence risks. For markdown files, missing warnings about behavior that can affect user data or privacy should be flagged.

Missing User Warnings

Medium

Confidence: 84% confidence
Finding: The Async Persistence section documents getItem, setItem, and removeItem operations against persistent storage but does not warn readers that application data will be retained on-device and may impact privacy or data lifecycle expectations. In markdown documentation, user-affecting data persistence behavior should be disclosed.

Missing User Warnings

Low

Confidence: 85% confidence
Finding: This markdown file documents use of persist middleware with browser localStorage and later async storage, which causes state to be written to client storage across sessions. The examples show how to enable persistence but do not warn that persisted state may contain user data and remain on-device until cleared.

Missing User Warnings

Low

Confidence: 81% confidence
Finding: The async persistence example performs getItem/setItem/removeItem operations against an async storage backend, which is a file- or device-backed write operation in many environments. The documentation presents the pattern without any caution about persistence, retention, or suitability for sensitive data.

Static analysis

No suspicious patterns detected.