ClawHub

My Diary

Security checks across malware telemetry and agentic risk

Overview

This is a straightforward local diary skill, with privacy caveats because diary entries are saved and read from a local plaintext JSON file.

Install only if you are comfortable storing diary entries in a local plaintext JSON file. Change the hardcoded storage path to a private location, protect the file yourself if the contents are sensitive, and review prompts carefully before displaying or deleting entries.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (2)

Vague Triggers

Medium
Confidence
91% confidence
Finding
The trigger phrase "My diary" / "我的日记" is broad enough to match ordinary conversation, which can cause unintended skill activation and expose or manipulate highly sensitive diary data without a clearly intentional command. In a diary skill, accidental invocation is especially risky because the content is private and the documented actions include viewing and deleting entries.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The README documents persistent storage on a specific local disk path but does not prominently warn users that diary contents will be written to disk and retained there. For a diary skill, this is sensitive personal data, so lack of explicit privacy disclosure can lead users to unknowingly store private information in a recoverable local file.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal