ClawHub
Back to skill

Security audit

taohopdong

Security checks for vulnerabilities and agentic risk

Overview

This skill is not clearly malicious, but it needs review because a Google Sheet contract workflow also automatically creates persistent Odoo CRM records.

Install only if you intend the agent to write to both Google Sheets and Odoo CRM. Before use, verify the Google account, spreadsheet target, Odoo database, and connector code, and require an explicit confirmation or dry run before any sheet update or CRM record creation.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Description-Behavior Mismatch

High
Confidence
97% confidence
Finding
The skill’s declared purpose is to look up company tax information and write it into a Google Sheet, but it also instructs the agent to automatically create or update Odoo CRM records. This is a scope expansion into a separate system with business side effects, which can cause unauthorized customer/opportunity creation and violate user expectations or least-privilege boundaries.

Context-Inappropriate Capability

High
Confidence
96% confidence
Finding
Automatically creating CRM customers and opportunities is not necessary to fulfill the stated task of tax lookup and contract-sheet entry. Because these actions create persistent business records, an attacker or mistaken user input could trigger unwanted pipeline entries, duplicate accounts, or pollution of operational CRM data.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The skill describes automatic writes to Google Sheets and Odoo without a clear warning that executing the workflow will modify external systems. Lack of explicit notice and confirmation increases the chance of unintended data modification, especially since the workflow chains multiple writes after scraping and parsing third-party data.

Static analysis

No suspicious patterns detected.