Back to skill

Security audit

White Stone Memory

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent personal memory skill with local markdown storage and an optional, disclosed vector-search feature, but users should be aware of the persistent memory and optional embedding-provider data flow.

Before installing, decide whether you want a persistent agent memory system at all. Keep sensitive secrets out of the memory files, resolve the daily-review directory mismatch, and only enable Gemini-based vector search if you are comfortable sending memory text to an external embedding provider.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The core documentation defines Daily Review files under memory/diary/[date].md, but the initialization and creation examples later use memory/daily. This is an active contradiction in the skill's own instructions and can cause the agent to write to a different location than the one the skill declares.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The rule explicitly requires all memory entries to be written in bilingual format and says it applies regardless of the original context language. This imposes a specific language policy without offering user choice or opt-in, which matches the locale/language policy violation criteria.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The optional vector search section expands the skill from local file-based memory into external/networked behavior by encouraging use of Gemini API keys and local Ollama HTTP access. That increases attack surface, creates data exfiltration risk for memory contents sent to embedding providers, and may cause agents to interact with services not expected from a simple memory skill.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

The skill description is presented entirely in Chinese, and the file does not indicate that the skill is region-specific or that users may choose another language. Under the policy rules, forcing a specific language without opt-in is a natural-language policy issue.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.