Back to skill

Security audit

checkers-sixty60

Security checks for vulnerabilities and agentic risk

Overview

This is a straightforward browser-shopping guide for Checkers Sixty60, with low-risk scoping issues but no hidden code, persistence, or deceptive behavior.

Before using this skill, make sure you want the agent to shop specifically on Checkers.co.za and confirm the delivery type, quantities, substitutions, and total before checkout or any payment step.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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
95% confidence
Finding

The skill description is broadly scoped to common shopping intents like groceries, cart management, and ordering from Checkers, which can cause the agent to invoke this skill for a wide range of generic retail requests without clear user confirmation. In a browser-automation purchasing skill, over-broad activation increases the risk of unintended navigation or purchase-related actions being taken in the wrong context.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
86% confidence
Finding

The instruction to default to Sixty60 unless the user specifically requests Hyper makes a fulfillment choice on the user's behalf, which can lead to incorrect ordering constraints, excluded products, or a mismatched delivery mode. In a purchasing workflow, silently imposing a default can materially affect item availability, basket composition, and whether the user's actual shopping goal is met.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.