Back to skill

Security audit

Web3 Marketing & GTM

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent Web3 marketing template, but it includes ready-to-use guidance that can expose wallet addresses and target users from on-chain behavior without consent safeguards.

Review and edit the templates before use: remove public wallet-address collection, require opt-in consent before direct outreach based on wallet activity, add opt-out language, and adapt posting schedules to the actual audience region. The skill does not appear to install code or access your machine, but its marketing outputs need privacy review before publishing.

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

Vague Triggers

Medium
Confidence
95% confidence
Finding
The skill’s trigger conditions are very broad and include casual, common-language requests, which increases the chance of accidental invocation outside the intended scope. In an agentic system, this can override more appropriate skills or cause the model to produce marketing outputs when the user asked a higher-level, ambiguous, or mixed-domain question, leading to misrouting and unsafe automation behavior.

Missing User Warnings

Medium
Confidence
96% confidence
Finding
The launch-day Discord script explicitly tells users to post their wallet address or ENS publicly in chat, which can unnecessarily expose persistent identifiers tied to on-chain activity. In a Web3 marketing context this is more dangerous because community managers may reuse the script as-is at scale, enabling deanonymization, targeted phishing, wallet profiling, and spam against early users.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The file recommends behavior-based outreach over Discord, Telegram, and X using wallet activity as the targeting signal, but it does not mention consent, privacy notice, opt-in/opt-out controls, or channel-specific messaging rules. In a Web3 marketing skill, this materially increases the risk that an agent will generate or operationalize privacy-invasive re-engagement campaigns that users did not expect, potentially causing harassment, trust erosion, or regulatory/compliance issues.

Natural-Language Policy Violations

Low
Confidence
94% confidence
Finding
The guidance says to schedule posts for specific EST time windows, which imposes a locale/timezone preference in natural language. The file does not indicate that EST is optional, adaptable to audience region, or justified as a region-specific campaign requirement.

Static analysis

No suspicious patterns detected.