ClawHub
Back to skill

Security audit

DoctorClaw Project Status

Security checks for vulnerabilities and agentic risk

Overview

This skill is a project-status reporting template that clearly matches its stated purpose, though users should configure data sources, recipients, and retention carefully.

Before installing, decide exactly which project sources, calendars, team members, delivery channels, and report schedule are allowed. Treat generated reports as potentially sensitive internal business records, especially if sent to Telegram, Discord, clients, or stored long-term.

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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill explicitly encourages daily automated status reporting using project tasks, calendars, and team activity, but it does not warn users that this implies recurring access to potentially sensitive business data. Because reports may include deadlines, blockers, workload, and internal project risks, users may unknowingly enable ongoing collection and redistribution of operational information.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The delivery/archive step states that the status board may be sent through configured channels and saved to persistent storage, but it provides no user-facing warning about external transmission or retention of potentially sensitive internal status information. This can expose project health, blockers, staffing constraints, and deadlines to unintended recipients or leave a persistent record without informed consent or retention controls.

Content

No source excerpt is available for this finding.