ClawHub
Back to skill

Security audit

node-inspect-debugger

Security checks for vulnerabilities and agentic risk

Overview

The verdict is suspicious because the scanner found that saved heap snapshots may expose sensitive process memory; this is a real privacy weakness, though the finding does not show malicious intent.

Consider whether you need heap snapshot guidance before installing. If you use it, treat snapshots as sensitive: limit access, avoid sharing or uploading them, and remove them when finished. The scan was partial because some local references could not be resolved, so the evidence is incomplete.

A.I.G

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

SkillSpector

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)

The heap-snapshot workflow saves process memory without warning that it can contain sensitive data.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

Heap snapshots can contain credentials, session tokens, personal data, and other sensitive objects from process memory. The workflow recommends writing a snapshot to a predictable temporary path without requiring restrictive permissions, controlled retention, or a warning against sharing it; exposure is possible through permissive file permissions or subsequent artifact uploads. Heap collection is legitimate in this debugging context, and the localhost inspector guidance reduces remote-access risk, but it does not protect the saved snapshot.

Content

No source excerpt is available for this finding.