ClawHub
Back to skill

Security audit

GDPR PCI Checklist

Security checks for vulnerabilities and agentic risk

Overview

This skill appears to be a straightforward compliance-checklist API wrapper that sends only a company type to a disclosed external service.

Before installing, users should understand that their company type will be sent to the provider's external API. Avoid entering sensitive internal details unless the provider's terms and data handling are acceptable for your organization.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

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

md
## References

- **Kong Route:** https://api.mkkpro.com/compliance/gdpr-pci-checklist
- **API Docs:** https://api.mkkpro.com:8015/docs

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The operation is described only as "Get Compliance List," which is too vague to reliably constrain when an agent should invoke it. Ambiguous API descriptions can cause over-broad or incorrect tool use, including sending user or organizational context to the skill in situations where a compliance checklist is not actually needed.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.