Back to skill

Security audit

Ts Sdk Account

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only Aptos SDK account/signing guide with expected secret-handling examples and no executable behavior.

Installers should treat this as benign SDK guidance, but should still handle Aptos private keys, serialized account hex, and mnemonics as full-control secrets: keep them out of frontend code, logs, source control, and shared prompts, and prefer wallet adapters or managed secret storage for production.

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
  • 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 (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The mnemonic example shows a seed phrase literal without an explicit warning that mnemonics are equivalent to full wallet control and must never be hardcoded, logged, shared, or used outside secure server-side tooling. In an account/signer skill, readers may copy the pattern directly, and seed phrase mishandling can lead to complete compromise of funds and all derived accounts.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.