ClawHub
Back to skill

Security audit

Nutrient OpenClaw

Security checks for vulnerabilities and agentic risk

Overview

This skill is a clearly scoped document-processing integration that discloses external uploads, credit use, credential handling, and per-call confirmation requirements.

Install only if you intend to use Nutrient DWS for document processing. Expect selected files or pages to be sent to Nutrient for most operations and to consume credits. Configure the API key only through protected settings or an approved secrets manager, and pay special attention before using redaction or signing because those workflows can have permanent or legal consequences.

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
  • System Prompt LeakageDirect Leakage, Indirect Extraction, Tool-Based Exfiltration
  • 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)

Direct Prompt Extraction

High
Category
System Prompt Leakage
Confidence
85% confidence
Finding

Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.

Content

Scanner excerpt · SKILL.md (reported line 99)May include surrounding context.

md
3. Stop and route to an approved signing workflow if certificate custody, qualified/electronic-signature compliance, identity proofing, countersignatures, or regulated retention is required. Obtain human/legal approval where applicable.
4. Only for a compatible use case, estimate and confirm the exact `nutrient_sign` call. Preserve the source and verify the resulting signature and visible appearance before release.

## Failure and output rules

- On authentication, quota, timeout, or server failure, preserve the source and partial evidence without exposing secrets.
- Diagnose from redacted errors and current manifest/tool schemas. Do not print configuration or environment values.

Static analysis

No suspicious patterns detected.