T09 · Insecure Skill Coding Practices
- Location
SKILL.md:79- Finding
Automatic Transmission of Potentially Sensitive Conversation Data
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This memory skill is purpose-aligned, but it can automatically send and persist conversation and profile data to a configurable EverMemOS server without clear user-control, retention, HTTPS, or authentication safeguards.
Install only if you are comfortable with an agent storing selected conversation content, preferences, and profile details in an EverMemOS server. Use a trusted HTTPS endpoint, require API authentication, disable or tightly review automatic memory capture, avoid storing secrets or regulated data, and ensure users can inspect and delete stored memories.
SKILL.md:79Automatic Transmission of Potentially Sensitive Conversation Data
SKILL.md:60Sensitive Memory Operations Do Not Enforce Secure Transport or Authentication
The skill presents itself as a production memory integration but does not warn users that conversation content may be stored remotely on an EverMemOS server. In a memory skill, failure to disclose remote persistence and transmission undermines informed consent and creates substantial privacy and compliance risk.
The document says the system will automatically record user profile information and preferences, but it gives no warning about the data impact of collecting this personal information. In this context, profiling and long-term storage are especially sensitive because they can accumulate behavioral and preference data over time without meaningful user awareness.
The curl example demonstrates sending message content directly to the EverMemOS API, including user-authored text and metadata. As documentation for a memory skill this is functional, but it normalizes remote transfer of conversational data without emphasizing secure transport, authentication, or user consent, which increases privacy risk in real deployments.
curl -X POST ${EVERMEMOS_URL}/api/v1/memories \
-H "Content-Type: application/json" \
-d '{
"message_id": "msg_001",
This code transmits memory content to an externally configured EverMemOS endpoint using requests.post, which can include user conversation data and identifiers. External transmission is expected for this skill, but it remains security-relevant because the endpoint is configurable, the default uses plain HTTP, and the example does not show authentication, consent checks, or data minimization.
"create_time": datetime.utcnow().isoformat() + "Z",
"scene": "assistant"
}
resp = requests.post(f"{EVERMEMOS_URL}/api/v1/memories", json=data)
return resp.json()
# 使用示例
The trigger phrases include broad everyday expressions such as “之前说过...”, “保存这个”, and “我的偏好是...”, which can cause the memory skill to activate unexpectedly during normal conversation. In this skill’s context, unintended activation is risky because it can lead to storage or retrieval of user data without a clear, explicit request.
The automatic memory triggers are vague and include sensitive situations like self-introduction, task completion, and preference expression without clear limits on what may be stored. Because this skill sends conversation content to a long-term memory system, ambiguous auto-save rules can cause overcollection of personal data and retention of information the user did not intend to persist.
The store method sends conversation content and user identifiers to the configured memory server. In a long-term memory skill this is expected behavior, but it is still dangerous if used without strong endpoint validation, encryption, and clear user authorization because it can persist sensitive conversation data outside the immediate chat environment.
def store(self, content, sender="user"):
"""存储记忆"""
return requests.post(
f"{self.base_url}/api/v1/memories",
json={
"message_id": f"msg_{int(time.time()*1000)}",
The recall method sends the user's query and identifier to the remote retrieval endpoint, exposing potentially sensitive search terms and linking them to a persistent profile. Although retrieval is core functionality, transmitting such queries externally without explicit disclosure and transport safeguards can leak sensitive interests or prior conversation context.
def recall(self, query, top_k=5):
"""检索记忆"""
return requests.post(
f"{self.base_url}/api/v1/memories/retrieve",
json={
"query": query,
文件中的名称、描述和触发短语均以中文固定表达呈现,尤其触发条件仅列出中文短语,没有说明是否支持其他语言或允许用户选择语言。若组织要求避免未经选择地强制特定语言/地区,这种默认中文约束可能构成语言策略问题。
No suspicious patterns detected.