ClawHub
Back to skill

Security audit

Cloud Data Migration

Security checks for vulnerabilities and agentic risk

Overview

This migration-planning skill is documentation-only and mostly purpose-aligned, but it needs review because some examples can expose database passwords and one validation step may modify data.

Review and revise the generated runbooks before use. Do not paste real passwords into command lines; prefer prompts, protected option files, or a secrets manager. Treat any sync or repair command, especially pt-table-sync with --execute, as a data-changing operation that requires backups, direction review, staging validation, and explicit approval. Confirm all cloud storage destinations and IAM profiles are owned and scoped to the intended migration.

A.I.G

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (2)

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:647
Finding

Database credentials exposed through command-line arguments

Content
View full analysis
tables.txt gsql -d your_database -U your_user -W your_password \ -f export_schema.sql > schema_dws.sql ``` ### Technical Analysis The documentation instructs operators to provide database passwords directly as command-line arguments. Although the values shown are placeholders rather than real secrets, operators following these templates are likely to replace them with production credentials. Command-line secrets can be exposed through: - Shell history files. - Process listings such as `ps`, `/proc`, and process-monitoring utilities. - Job execution logs and terminal session recordings. - CI/CD logs and command tracing. - Operational telemetry collected by monitoring or endpoint-security agents. - Copied command transcripts, tickets, and runbooks. The `gsql` examples are particularly misleading because `-W` is commonly intended to request an interactive password prompt; placing a password directly after it encourages insecure handling and may not behave as intended across versions. ### Attack Path 1. An o ...[truncated 1244 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
SKILL.md:653
Finding

Destructive data synchronization command presented as a validation step

Content
View full analysis
Remediation
View remediation

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 (4)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The skill title, core description, and most operational guidance are presented bilingually but heavily centered on Chinese, and the required/input sections later continue primarily in Chinese. There is no statement that users may choose their preferred language, so the skill imposes a locale/language assumption rather than offering opt-in choice.

Content

No source excerpt is available for this finding.

Cloud Storage Exfiltration

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is uploaded to cloud storage (S3 / GCS / Azure Blob). This may be a legitimate backup or exfiltration to an external bucket. Manual review is recommended.

Content

Scanner excerpt · examples.md (reported line 747)May include surrounding context.

Step 3: 上传至AWS S3

bash
# 使用AWS CLI上传
aws s3 sync ./local-export/ s3://your-redshift-bucket/import/ \
  --profile your-profile

# 或使用S3控制台批量上传

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

The document content begins in Chinese and the examples throughout are written predominantly in Chinese, while only partial English labeling is provided. This can conflict with a language or locale policy if the skill output is effectively constrained to Chinese without stating that users may choose their preferred language.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The file is predominantly written in Chinese, with only limited bilingual headings, which effectively imposes a specific language choice on users consuming the skill content. There is no statement offering an alternative language version or explaining a region-specific requirement that would justify the locale constraint.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.