{ "skill_name": "supermemory", "skill_path": "/workspace/skills/clawhub-supermemory", "skill_directory": "/workspace/skills/clawhub-supermemory", "is_safe": false, "max_severity": "CRITICAL", "findings_count": 4, "findings": [ { "id": "llm_finding_supermemory_0", "rule_id": "LLM_DATA_EXFILTRATION", "category": "data_exfiltration", "severity": "CRITICAL", "title": "Hardcoded API Key Exposed in Documentation", "description": "The SKILL.md file contains a hardcoded SuperMemory API key (sm_oiZHA2HcwT4tqSKmA7cCoK_opSRFViNFNxbYqjkjpVNfjSPqQWCNoOBAcxKZkKBfRVVrEQDVxLWHJPvepxqwEPe) in the setup instructions. This is a live credential that provides full access to the SuperMemory API account. Anyone with access to this skill can use this key to access, modify, or delete memories, potentially exposing sensitive user data stored in the SuperMemory service.", "file_path": "SKILL.md", "line_number": 9, "snippet": "export SUPERMEMORY_API_KEY=\"sm_oiZHA2HcwT4tqSKmA7cCoK_opSRFViNFNxbYqjkjpVNfjSPqQWCNoOBAcxKZkKBfRVVrEQDVxLWHJPvepxqwEPe\"", "remediation": "Immediately revoke the exposed API key through the SuperMemory dashboard. Remove the hardcoded key from documentation. Update instructions to guide users to obtain their own API keys from SuperMemory. Never include live credentials in example code - use placeholder values like 'your-api-key-here' instead.", "analyzer": "llm", "metadata": { "model": "claude-sonnet-4-5-20250929", "overall_assessment": "This skill presents CRITICAL security risks due to a hardcoded API key exposure and HIGH risks from potential data exfiltration to third-party servers. The hardcoded credential (sm_oiZHA2HcwT4tqSKmA7cCoK_opSRFViNFNxbYqjkjpVNfjSPqQWCNoOBAcxKZkKBfRVVrEQDVxLWHJPvepxqwEPe) must be revoked immediately. The skill encourages storing sensitive data (including API keys) in an external service without adequate warnings about data handling or privacy implications. Additional concerns include command injection risks in bash scripts and misleading documentation that promotes insecure practices. The skill requires immediate remediation before safe use.", "primary_threats": [ "Hardcoded API Key Exposure", "Data Exfiltration to Third-Party Service", "Command Injection Vulnerability", "Misleading Security Guidance" ], "aitech": "AITech-8.2", "aitech_name": "Data Exfiltration / Exposure", "aisubtech": "AISubtech-8.2.3", "aisubtech_name": "Data Exfiltration via Agent Tooling", "scanner_category": "SECURITY VIOLATION", "meta_validated": true, "meta_confidence": "HIGH", "meta_confidence_reason": "LLM analyzer confirmed this is a real, hardcoded API key in documentation. The key format matches SuperMemory's pattern (sm_*) and is exposed in a public-facing file. This is unambiguous credential exposure.", "meta_exploitability": "Trivial - key is publicly visible in the skill package, no authentication required to access", "meta_impact": "Critical - full access to the SuperMemory account, can read/write/delete all stored memories, potential exposure of sensitive user data" } }, { "id": "llm_finding_supermemory_1", "rule_id": "LLM_DATA_EXFILTRATION", "category": "data_exfiltration", "severity": "HIGH", "title": "Potential Data Exfiltration via Third-Party API", "description": "The skill sends user content and queries to an external third-party API (api.supermemory.ai) without explicit user consent or data handling disclosure. Users may unknowingly store sensitive information (API keys, passwords, personal data) in their 'memories' which are then transmitted to and stored on external servers. The example usage even suggests storing API credentials: 'Remember that my API key is xyz'. This creates a significant data exposure risk.", "file_path": "scripts/add-memory.sh", "line_number": null, "snippet": "Example from SKILL.md: 'Remember that my API key is xyz' \u2192 supermemory add 'My API key is xyz'. All scripts make POST requests to https://api.supermemory.ai with user content.", "remediation": "Add prominent warnings in SKILL.md about data being sent to external servers. Explicitly warn users NOT to store credentials or sensitive data. Include a privacy/data handling section explaining what data is transmitted and stored externally. Consider implementing local filtering to detect and warn about sensitive data patterns (API keys, passwords) before transmission.", "analyzer": "llm", "metadata": { "model": "claude-sonnet-4-5-20250929", "overall_assessment": "This skill presents CRITICAL security risks due to a hardcoded API key exposure and HIGH risks from potential data exfiltration to third-party servers. The hardcoded credential (sm_oiZHA2HcwT4tqSKmA7cCoK_opSRFViNFNxbYqjkjpVNfjSPqQWCNoOBAcxKZkKBfRVVrEQDVxLWHJPvepxqwEPe) must be revoked immediately. The skill encourages storing sensitive data (including API keys) in an external service without adequate warnings about data handling or privacy implications. Additional concerns include command injection risks in bash scripts and misleading documentation that promotes insecure practices. The skill requires immediate remediation before safe use.", "primary_threats": [ "Hardcoded API Key Exposure", "Data Exfiltration to Third-Party Service", "Command Injection Vulnerability", "Misleading Security Guidance" ], "aitech": "AITech-8.2", "aitech_name": "Data Exfiltration / Exposure", "aisubtech": "AISubtech-8.2.3", "aisubtech_name": "Data Exfiltration via Agent Tooling", "scanner_category": "SECURITY VIOLATION", "meta_validated": true, "meta_confidence": "MEDIUM", "meta_confidence_reason": "LLM analyzer correctly identified that data is sent to external servers. However, this is the INTENDED functionality of the skill (integrating with SuperMemory API). The issue is lack of disclosure, not unauthorized exfiltration. Downgraded from HIGH to MEDIUM severity because this is documented behavior (the skill is explicitly for SuperMemory integration).", "meta_exploitability": "Low - this is intended functionality, not a vulnerability. Risk comes from user misunderstanding, not exploitation", "meta_impact": "Medium - potential exposure of sensitive data if users don't understand where their data goes" } }, { "id": "llm_finding_supermemory_2", "rule_id": "LLM_COMMAND_INJECTION", "category": "command_injection", "severity": "MEDIUM", "title": "Command Injection Risk in Bash Scripts", "description": "The bash scripts use user-provided input directly in JSON payloads and shell commands without proper sanitization. While the scripts use double quotes, special characters in user input (like double quotes, backticks, or dollar signs) could break out of the JSON structure or be interpreted by the shell. The CONTENT and QUERY variables are directly interpolated into JSON without escaping.", "file_path": "scripts/add-memory.sh", "line_number": null, "snippet": "DATA=$(cat <