Security audit

Go Exa

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Go integration guide for the Exa API, with disclosed network use and API-key handling.

Use this only for Go projects where you intend to call Exa. Keep EXA_API_KEY in a secure environment variable, do not commit or log it, avoid sending secrets or private data in search prompts or URLs, and remember that Exa calls may incur account billing, especially research tasks.

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
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

Low

Category: Not specified by scanner
Confidence: 79% confidence
Finding: This markdown file instructs users to export EXA_API_KEY and send it as x-api-key or Authorization: Bearer <key> but does not include any caution about protecting the secret, avoiding commits/logging, or using secure storage. Because markdown files should warn about behaviors affecting privacy or sensitive data, the omission is a quality/safety issue.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.