other
- Location
SKILL.md:202- Finding
Undisclosed Persistent Workspace Activity Logging
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 202-208
Vulnerability Type: Persistent workspace activity logging
Risk Level: LowRelevant instruction, translated into English from the source:
text After completing each generation task, append a daily record to working memory: - File path and content summary - Problems discovered and corrected, if any - Counts of questions and diagrams Memory file path: {workspace}/.workbuddy/memory/YYYY-MM-DD.mdTechnical Analysis
The Skill requires every completed generation task to append metadata to a hidden, persistent file under the user's workspace. The recorded information includes the generated file path, a content summary, correction history, and document statistics.
This write is not necessary to generate, validate, preview, or deliver the requested mathematics document. It is also not disclosed in
README.md, meaning a user may reasonably invoke the Skill without expecting persistent activity records to be created.The behavior is not classified as
T02: Agent Memory Poisoningbecause the identified instructions do not write attacker-controlled behavioral rules intended to influence future agent sessions. It is instead classified as an unlisted privacy and workspace-modification issue.Attack Path
- A user invokes the Skill to generate mathematics review material.
- The Skill creates and validates the requested HTML document.
- Stage 6 instructs the agent to append task metadata to
.workbuddy/memory/YYYY-MM-DD.md. - The persistent record may contain user topic information, generated filenames, workspace paths, and correction history.
- A later agent session or another process with workspace read access can inspect this retained activity history without requiring the original conversation.
No external exfiltration, privilege escalation, or executable persistence was identified.
Impact Assessment
The behavio ...[truncated 675 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the mandatory Stage 6 memory-write requirement unless persistent recording is essential to the Skill's documented purpose.
- Make activity logging explicitly opt-in and request user consent before creating or updating a memory file.
- Disclose the exact destination, retained fields, purpose, and retention period in both
README.mdandSKILL.md. - Record only minimal, non-sensitive metadata; avoid content summaries, absolute paths, user-provided text, and correction details.
- Use a user-approved storage location rather than a hidden workspace directory.
- Provide a mechanism to inspect, disable, and delete retained records.
- Prevent generated or user-controlled content from being stored as future behavioral instructions.
- If logging remains enabled, apply restrictive file permissions appropriate to the host environment.