Back to skill

Security audit

Eition_Emo

Security checks for vulnerabilities and agentic risk

Overview

This skill is not malicious, but it asks the agent to automatically monitor conversations and keep sensitive emotional records with too little user control.

Install only if you are comfortable with an agent passively analyzing normal conversations and saving sensitive emotional records locally. Prefer enabling it only with explicit confirmation, review entries before they are written, and use a pinned installer version if available.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (2)

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:115
Finding
Automatic Collection and Persistent Storage of Sensitive Conversation and Mental-Health Data## Vulnerability Details **File Location**: `SKILL.md:21`, `SKILL.md:115-122`, `SKILL.md:172-179`; corroborating behavior in `README.md:34` and `README.md:115` **Vulnerability Type**: Excessive access to conversations and sensitive local data **Risk Level**: Medium ### Vulnerable Instructions The following is a faithful English translation of the relevant source instructions: ```markdown - Automatically reads your `memory/emotions/` folder **Trigger event, including the specific time, place, and person:** - Time: - Place: - Person: - Exact words: - My reaction: ### On every heartbeat, every 30 minutes - [ ] Scan recent conversations and identify emotional signals - [ ] If strong emotions are detected, execute the correction process - [ ] Automatically record the result in log.md ### Run once daily, at 10:00 PM - [ ] Ask: "What are three small things you accomplished today?" - [ ] If the user does not respond, automatically summarize them from conversations - [ ] Write the result to wins.md - [ ] Estimate a mood score from 1 to 10 ``` ### Technical Analysis The Skill directs an agent to inspect recent conversation history and the persistent `memory/emotions/` directory automatically. It then extracts and stores sensitive information, including emotional state, physical symptoms, locations, identities of other people, exact quotations, and internal thoughts. This behavior is not limited to messages explicitly selected by the user. The scheduled heartbeat workflow performs recurring scans, while the daily workflow may infer and save information even when the user does not respond. This breaks least-privilege principles because a general emotional-support function does not inherently require continuous access to the entire recent conversation history or storage of identifying details. The claim that records remain local does not eliminate the risk. Predictable plaintext files may be available to other l ...[truncated 1244 chars]
Remediation
## Remediation Suggestions 1. Disable automatic conversation scanning by default and require explicit, informed opt-in. 2. Process only the current message or a conversation segment selected by the user. 3. Request separate consent before enabling heartbeat monitoring, mood inference, or persistent logging. 4. Minimize collected data by omitting names, exact quotations, locations, and third-party information unless strictly required. 5. Show the proposed log entry and obtain confirmation before writing it. 6. Provide controls to pause monitoring, inspect collected records, correct inferred data, and permanently delete all records. 7. Apply restrictive filesystem permissions and document which agents, Skills, synchronization systems, and backup processes can access the directory. 8. Define an explicit retention policy and allow users to shorten retention or disable storage entirely. 9. Avoid generating mood scores or accomplishments from silence; require user confirmation for inferred mental-health records.

T08 · Insecure Dependencies

Warning
Location
SKILL.md:288
Finding
Mutable Third-Party Package Is Downloaded and Executed Through npx## Vulnerability Details **File Location**: `SKILL.md:288-295` and `README.md:55-62` **Vulnerability Type**: Unpinned executable dependency **Risk Level**: Medium ### Vulnerable Code ```bash npx clawhub@latest install Eition_Emo ``` The surrounding instructions state that installation creates the `memory/emotions/` directory, creates `HEARTBEAT.md`, and integrates the emotional-correction workflow into conversations. ### Technical Analysis The documented installation command uses `npx`, which may download and execute package code from a package registry. The `@latest` tag is mutable, so the package version executed by a future user can differ from the version reviewed during this audit. No exact package version, integrity hash, lockfile, reviewed installer artifact, expected publisher identity, or registry restriction is provided. Consequently, the effective installer payload remains under the control of future registry releases and package-account security. This finding does not prove that the current `clawhub` package is malicious. The vulnerability is the unsafe trust model: installation executes a remotely resolved and changeable third-party dependency without reproducible version or integrity verification. ### Attack Path 1. An attacker compromises the package publisher account, registry entry, or release process for `clawhub`. 2. The attacker publishes a malicious release and assigns it to the `latest` distribution tag. 3. A user follows the documented `npx clawhub@latest install Eition_Emo` command. 4. `npx` resolves and downloads the attacker-controlled release. 5. Package entry-point or lifecycle code executes with the invoking user's permissions. 6. The malicious release can access files, environment variables, network resources, and credentials available to that user. ### Impact Assessment Successful exploitation could provide arbitrary code execution with the permissions of the user running the ins ...[truncated 475 chars]
Remediation
## Remediation Suggestions 1. Replace `@latest` with an exact, reviewed package version. 2. Publish and verify the expected package integrity hash before execution. 3. Document the trusted registry, canonical package name, and verified publisher identity. 4. Provide a lockfile or reproducible installation manifest. 5. Review package entry points and lifecycle scripts for the pinned release. 6. Prefer downloading and inspecting a signed installer artifact before executing it. 7. Run installation in a restricted environment without unnecessary credentials or filesystem access. 8. Establish a controlled update process in which new package versions are audited before documentation is changed to reference them.
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (12)

Missing User Warnings

High
Confidence
96% confidence
Finding
The skill advertises automatic reading of `memory/emotions/` and emotion detection from conversation but does not present a clear, prominent upfront warning that highly sensitive mental-health-related content will be monitored and stored. Because the collected data includes emotional states and personal reflections, insufficient notice undermines informed consent and materially increases privacy risk.

Ssd 3

High
Confidence
98% confidence
Finding
The logging template directs capture of highly sensitive details including time, place, people, exact quotes, bodily symptoms, and internal thoughts. This level of detail creates a rich dossier of psychological and interpersonal information that could seriously harm the user if exposed, misused, or retained longer than necessary.

Vague Triggers

Medium
Confidence
95% confidence
Finding
The skill claims it will automatically detect emotional signals during normal conversation without requiring explicit invocation, which creates an overly broad trigger boundary. This can cause the agent to process and retain sensitive mental-health disclosures by default, including in contexts where the user did not intend to activate tracking.

Ssd 3

Medium
Confidence
95% confidence
Finding
The skill states that ordinary conversation will be automatically recognized and recorded for emotion tracking, which by design captures potentially sensitive mental-health content by default. Because the skill is positioned for emotionally vulnerable users, indiscriminate background logging materially raises privacy and safety risk.

Ssd 3

Medium
Confidence
94% confidence
Finding
The README says that if the user does not reply, the system will automatically summarize prior conversation content and write it to a log. That behavior creates a data-retention risk because sensitive personal disclosures may be persisted without contemporaneous confirmation, increasing exposure to later leakage, misuse, or unintended access.

Rp1

Medium
Category
MCP Rug Pull
Confidence
93% confidence
Finding
The README instructs users to install via `npx clawhub@latest`, which fetches the latest package version at execution time rather than a reviewed, pinned release. This creates a supply-chain risk: a compromised upstream package or malicious future update could execute unexpected code during installation.

Intent-Code Divergence

Medium
Confidence
87% confidence
Finding
The README makes a strong privacy guarantee that all data remains local and is never uploaded, while elsewhere describing automatic conversation summarization and logging without technical evidence or implementation details to support that claim. In a mental-health-oriented skill, inaccurate privacy assurances can mislead users into disclosing highly sensitive information under false assumptions.

Ssd 3

Medium
Confidence
97% confidence
Finding
The skill instructs automatic scanning of conversations and storage of sensitive emotional disclosures into long-term memory files. Even if stored locally, automatic persistence of mental-state information creates privacy and security risk because the data may later be accessed, reused, or exposed beyond the user's immediate expectation.

Vague Triggers

Medium
Confidence
94% confidence
Finding
The automatic trigger keywords are broad, common phrases that can appear in ordinary conversation, causing the skill to activate unexpectedly. In this skill's context, false triggering is risky because activation leads to analysis and persistence of sensitive emotional data, increasing privacy exposure without clear user intent.

Ssd 3

Medium
Confidence
95% confidence
Finding
The heartbeat behavior mandates continuous monitoring of recent dialogue and automatic summarization into stored records even when the user has not replied. This creates ongoing passive collection of sensitive emotional and behavioral data, increasing the chance of over-collection and violating user expectations of when analysis is happening.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The daily and weekly automation describes summarizing conversations, estimating mood, generating reports, and storing them persistently, but does not pair those behaviors with sufficiently explicit warning and consent controls. Persistent behavioral profiling over time is especially sensitive in a mental-health-adjacent skill and can expose patterns the user may not expect to be retained.

Rp1

Medium
Category
MCP Rug Pull
Confidence
95% confidence
Finding
The install command uses `npx clawhub@latest`, which fetches and executes the latest published package version without pinning. This creates a supply-chain risk: a compromised publisher account, malicious update, or breaking release could cause users to run unintended code at install time.