Back to skill

Security audit

Connect agents over A2A

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only skill for troubleshooting A2A agent connections, with credential-handling risks that are disclosed enough to manage.

Install only if you need A2A agent-connection guidance. When using it, treat bearer tokens as credentials, keep agent-card URLs on HTTPS, store tokens in approved secret storage, and avoid putting token values in notes, logs, or chat messages.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
83% confidence
Finding

The description says to use the skill when a task needs something only another agent can do, or when told to 'link' two agents and setup is not working. This activation guidance is broad and lacks explicit constraints or negative examples, so it could overlap with ordinary troubleshooting or collaboration requests and cause unintended invocation.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
76% confidence
Finding

The markdown explains that peers may send bearer tokens in the clear and later instructs readers to record how the token is stored, but it does not include a clear warning to protect credentials or avoid exposing secrets in logs, notes, or insecure channels. Because the skill deals directly with authentication material and possible plaintext transmission, a user-facing warning is warranted.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.