Back to skill

Security audit

Data Migration Planner

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only data migration planning skill with no executable code, persistence, credential handling, or hidden behavior.

Before using this for a real migration, treat the generated runbook as planning material: have qualified operators review it, run tests outside production first, confirm backups and rollback steps, and apply privacy/compliance controls for sensitive data.

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
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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 (1)

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill explicitly plans and validates data migrations involving source and target systems, ETL execution, rollback, and production cutover, but it does not include safety boundaries or warnings about operating on sensitive, regulated, or production data. In an agent context, this omission can lead users or downstream automation to apply the guidance directly against live systems without adequate approval, backups, access controls, or privacy review, increasing the chance of data loss, corruption, exposure, or compliance violations.

Static analysis

No suspicious patterns detected.