Back to skill

Security audit

Google Pay

Security checks for vulnerabilities and agentic risk

Overview

This Google Pay skill is a disclosed implementation guide with payment-safety guardrails, local notes, and no hidden execution behavior.

Install this skill only for a project where you intend to integrate Google Pay and trust your Google Pay, PSP, and backend accounts. Keep it in test mode until the validation checklist passes, and do not put raw payment tokens, private keys, or PSP secrets into the local notes or chat.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 51)May include surrounding context.

md
- CLI tools for diagnostics: `curl`, `jq`
- Access to Google Pay business console and target PSP account

Never ask users to paste private keys, full token payloads, or PSP secrets into chat.

## Data Storage

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
80% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · setup.md (reported line 35)May include surrounding context.

bash
mkdir -p ~/google-pay
touch ~/google-pay/{memory.md,implementations.md,validation-log.md,incidents.md}
chmod 700 ~/google-pay
chmod 600 ~/google-pay/{memory.md,implementations.md,validation-log.md,incidents.md}

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
80% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · setup.md (reported line 36)May include surrounding context.

mkdir -p ~/google-pay touch ~/google-pay/{memory.md,implementations.md,validation-log.md,incidents.md} chmod 700 ~/google-pay chmod 600 ~/google-pay/{memory.md,implementations.md,validation-log.md,incidents.md}

text

5. If `memory.md` is empty, initialize it from `memory-template.md`.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · setup.md (reported line 58)May include surrounding context.

md
## Guardrails

- Never ask the user to expose private keys in chat.
- Never store raw Google Pay token payloads in local notes.
- Never claim production readiness without validation evidence.

Static analysis

No suspicious patterns detected.