ClawHub
Back to skill

Security audit

customer-crm

Security checks across malware telemetry and agentic risk

Overview

This skill is a coherent CRM/source-tracking integration that stores customer attribution data locally, with privacy and scoping details users should review.

Install this only in an environment where it is acceptable to persist customer identifiers, order history, source attribution, and repurchase-trigger data locally. Review the storage paths and add operational controls for retention, deletion, tenant isolation, and access to the generated CRM files.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Lp3

Medium
Category
MCP Least Privilege
Confidence
95% confidence
Finding
The skill declares tools `read, exec` and documents persistent writes to local JSON files, yet there is no explicit permissions model or narrowing of allowed file paths/operations. This creates a real risk of unauthorized customer-data read/write behavior, especially because the skill processes tenant and customer identifiers that could influence file access decisions.

Vague Triggers

Medium
Confidence
81% confidence
Finding
The manifest description uses broad trigger language such as post-delivery callbacks, public-account interaction, and repurchase recommendation without clearly limiting when the skill may run or what data/actions are in scope. In a CRM context handling customer records and attribution, vague triggering increases the chance of over-collection, unintended activation, and processing data outside user expectations.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The documentation explicitly states that customer source and profile data are written to local files, including per-tenant state and source-tracking mappings, but provides no user-facing notice about persistence, retention, or sensitivity. Because this is CRM data tied to customer identities and behavioral attribution, undisclosed local storage raises privacy, compliance, and accidental exposure risks.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.