Back to skill

Security audit

Openclaw Test Heap Leaks

Security checks for vulnerabilities and agentic risk

Overview

The verdict is suspicious because the scanner found that heap snapshots may retain sensitive data without a warning or safeguards; no malicious behavior was reported, but the review is incomplete.

Consider the risk that diagnostic snapshots could contain secrets or personal data before installing. The scanner recommends using synthetic test data, restricting snapshot access, reviewing before sharing, and deleting snapshots when finished. The analysis was partial because some referenced paths were unavailable, so the findings do not establish that the artifact is safe.

Vulnerability Patterns
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Heap snapshot collection lacks a warning about sensitive data persisted in diagnostic artifacts.

Medium
Category
Output Handling
Confidence
88% confidence
Finding

Heap snapshots can persist sensitive in-memory values, including credentials, tokens, and user data, but the workflow provides no warning or handling safeguards for these artifacts. Exposure could occur if snapshots are committed, included in CI artifacts, or shared during debugging; the supplied file does not instruct such disclosure. Local test-focused collection reduces the risk, although the runtime harness workflow broadens the potential scope of captured data.

Content

No source excerpt is available for this finding.