ClawHub
Back to skill

Security audit

Self Reflection 1.1.1

Security checks across malware telemetry and agentic risk

Overview

The skill’s reflection behavior is mostly coherent, but users should review it because its setup points to an external command outside the scanned package and it stores long-lived agent memory.

Install only after reviewing and pinning the external CLI source you plan to run. Enable the heartbeat only if recurring self-reflection is desired, and avoid logging secrets, customer data, private prompts, incident details, or proprietary workflow notes in the memory file.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Rogue AgentSelf-Modification, Session Persistence
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The README explicitly instructs users to persist reflections and lessons to disk, and the examples encourage storing operational mistakes, fixes, and possibly security-related lessons in a long-lived markdown file. Because reflective logs can easily contain sensitive prompts, internal errors, security incidents, or proprietary workflow details, the lack of a clear warning, minimization guidance, or access-control recommendation creates a real privacy and security risk.

Session Persistence

Medium
Category
Rogue Agent
Content
# Add to PATH
ln -sf ~/.openclaw/skills/self-reflection/bin/self-reflection ~/bin/self-reflection

# Create config
cp ~/.openclaw/skills/self-reflection/self-reflection.example.json ~/.openclaw/self-reflection.json
```
Confidence
80% confidence
Finding
This section instructs users to create a persistent config file and integrate the skill into a recurring heartbeat flow, which normalizes ongoing storage of state and reflection data across sessions. While persistence is part of the feature, documenting it without prominent security guidance makes it more likely that sensitive operational history will be retained indefinitely in predictable local paths.

Session Persistence

Medium
Category
Rogue Agent
Content
## Configuration

Create `~/.openclaw/self-reflection.json`:

```json
{
Confidence
92% confidence
Finding
The configuration example hard-codes persistent paths for both the memory log and state file, encouraging durable session history in user home and workspace directories. In the context of a self-reflection skill, these files are likely to accumulate sensitive internal mistakes, security notes, or workflow context, so predictable long-term storage increases exposure if the host is shared, backed up, synced, or otherwise accessible.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.