T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:109- Finding
Historical Conversation Access and Covert Ongoing Personality Profiling
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed personality-profiling tool, but it includes under-scoped background and historical conversation analysis plus unsafe helper scripts that deserve careful review before installation.
Install only if you intentionally want an agent to analyze conversations into a persistent personality profile. Prefer manual mode, avoid historical scans unless you select the exact data yourself, store outputs in a protected location, and do not run the shell scripts with untrusted filenames or arguments until they are fixed.
SKILL.md:109Historical Conversation Access and Covert Ongoing Personality Profiling
scripts/extract.sh:68Arbitrary Python Code Execution Through Extraction Script Arguments
scripts/distill.sh:44Arbitrary Python Code Execution Through Distillation Script Arguments
README.md:14Mutable and Unverified Third-Party Dependency Installation
The background mode states that daily conversations can be scanned and traits extracted '在用户无感知的情况下完成提取'—without user awareness. Covert, ongoing psychological profiling from routine conversations is highly invasive and incompatible with informed consent, making this the most serious issue in the skill.
The README promotes scanning historical conversations and extracting personality traits, including sensitive behavioral and psychological inferences, without an explicit privacy warning or informed-consent flow. In this skill context, the feature is specifically designed to profile users from past communications, which makes omission of data-impact disclosure materially dangerous.
The README presents daily/weekly automatic extraction, ongoing monitoring, change detection, and monthly evolution reports as normal usage without a clear warning that this constitutes recurring behavioral surveillance and profile generation. In a memory/personality skill, automation substantially increases privacy risk because collection expands over time and may capture sensitive changes in mental state, habits, relationships, and health-related cues.
This mismatch specifically mentions undeclared persistent storage of validation history to disk, which is security-relevant because it expands retention of derived behavioral data beyond the user-facing description. Hidden or insufficiently disclosed persistence of profiling metadata increases privacy risk and reduces informed consent.
This mismatch specifically mentions undeclared persistent storage of validation history to disk, which is security-relevant because it expands retention of derived behavioral data beyond the user-facing description. Hidden or insufficiently disclosed persistence of profiling metadata increases privacy risk and reduces informed consent.
This mismatch specifically mentions undeclared persistent storage of validation history to disk, which is security-relevant because it expands retention of derived behavioral data beyond the user-facing description. Hidden or insufficiently disclosed persistence of profiling metadata increases privacy risk and reduces informed consent.
This mismatch specifically mentions undeclared persistent storage of validation history to disk, which is security-relevant because it expands retention of derived behavioral data beyond the user-facing description. Hidden or insufficiently disclosed persistence of profiling metadata increases privacy risk and reduces informed consent.
This mismatch specifically mentions undeclared persistent storage of validation history to disk, which is security-relevant because it expands retention of derived behavioral data beyond the user-facing description. Hidden or insufficiently disclosed persistence of profiling metadata increases privacy risk and reduces informed consent.
The description presents the skill as personality modeling and memory distillation without prominently warning that it analyzes conversations, infers sensitive traits, and stores persona profiles. Users cannot give informed consent if the privacy implications are omitted from the primary description.
The workflow begins as casual conversation and incrementally builds toward personality extraction and eventual background profiling. This gradual escalation can cause users to disclose sensitive information under a low-risk framing before realizing it will be converted into a persistent psychological profile.
The instructions explicitly direct the AI to scan prior conversations for work habits, life history, emotions, relationships, and self-reflection, then extract and persist those into a structured profile. This is sensitive personal-data processing and psychological profiling, which can reveal intimate attributes far beyond ordinary chat assistance.
The background automatic extraction section introduces ongoing profiling but does not provide a strong, explicit warning about continuous privacy impact. This is especially risky because one documented mode says extraction may occur 'without user awareness,' undermining informed consent and user control.
The skill documents persistent storage of fossils and persona profiles, including source quotes and timeline data, without a prominent retention warning. Retaining such detailed personal and inferred data increases harm in the event of unauthorized access, secondary use, or prolonged profiling.
The document promotes extraction of personality traits, autobiographical memory, emotional dynamics, social network data, and long-term evolution from user conversations, but provides no consent, minimization, retention, or privacy warning. Because this skill is specifically designed for sensitive inference and profiling, omission of safeguards materially increases the risk of covert surveillance, over-collection, and misuse of highly sensitive derived data.
The example workflow writes generated personality reports to local files such as profile.md without any warning that these files may contain sensitive inferred psychological and behavioral data. Storing such reports in plaintext or unmanaged local locations can expose users to unauthorized access, secondary use, and long-term persistence of intimate profile information.
The best-practice section explicitly recommends automatic daily extraction from logs and periodic distillation, encouraging continuous analysis of sensitive personal content without discussing consent, scope limits, or review controls. In the context of a profiling skill, this makes the behavior more dangerous because it normalizes ongoing background monitoring and accumulation of sensitive inferences over time.
Artifact content does not match its filename extension
The README instructs users to install and run npx clawhub install soul-fireseed without pinning a specific package version or integrity mechanism. This creates a supply-chain risk: users may fetch a changed or compromised package at install time, and because the command is framed as a one-line installation path, many users are likely to execute it without review.
This repeats an unpinned npx clawhub install soul-fireseed invocation in the primary installation instructions. Repetition in setup guidance increases the likelihood that users will execute an implicitly trusted remote package fetch, exposing them to package substitution or malicious updates.
This section encourages broad collection of conversation content, memory analysis, automatic recurring extraction, and persistent persona generation. While these are core features, the guidance normalizes expansive profiling and retention without minimization boundaries, making overcollection a real security/privacy weakness in the context of a personality-modeling skill.
The community/ecosystem section again references npx clawhub install soul-fireseed without a pinned version, reinforcing unsafe installation behavior. Even in non-install sections, executable commands can be copied directly by users and carry the same supply-chain exposure.
The examples show generating and writing evolution/personality outputs to files, which are likely to contain sensitive inferred personal data, but do not warn about storage security or secondary disclosure risks. Inferred traits and longitudinal reports can be more sensitive than raw conversation snippets because they condense intimate attributes into easy-to-share artifacts.
The later examples and best-practice guidance encourage preserving complete historical records, exporting profiles, backing up fossil data, and storing conversation-derived artifacts in databases. In this skill context, those records are directly tied to identity, behavior, and inferred traits, so broad retention and export materially increase breach impact and misuse potential.
The skill documentation describes reading prior conversations and writing extracted 'fossils' and persona profiles to local storage, but it does not declare any explicit tool scope or permissions. This creates a governance gap: a host may grant broader file capabilities than users expect, enabling silent access to conversation history and persistent profiling artifacts.
The activation phrases include broad terms like '灵魂', '人格建模', and '数字孪生' that could appear in ordinary conversation and unintentionally trigger the skill. In this context, accidental invocation is dangerous because the skill performs profiling and may transition users toward sensitive memory analysis and persistent storage.
No suspicious patterns detected.