Security audit

gurkerlcli

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent grocery-shopping CLI helper, but it asks users to expose and persist account passwords in unsafe ways.

Review before installing. Prefer interactive login or an OS credential manager, avoid putting the Gurkerl password in shell history, environment variables, or ~/.env.local, and verify the external gurkerlcli package source/version before use. Treat cart and list commands as authenticated account changes.

A.I.G

Vulnerability Patterns

Insecure DependenciesIntroduces malicious components through unsafe dependency sources
Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
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

Findings (2)

T08 · Insecure Dependencies

Warning

Location: SKILL.md:14
Finding: Unpinned Third-Party CLI Installation Creates a Supply-Chain Risk
Content: View full analysis
Remediation: View remediation

T09 · Insecure Skill Coding Practices

Warning

Location: SKILL.md:27
Finding: Authentication Instructions Expose Account Passwords Through Unsafe Input and Storage Channels
Content: View full analysis
Remediation: View remediation

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

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The skill explicitly recommends storing login credentials in environment variables or a persistent local file (~/.env.local) without warning about exposure risks. Environment variables can leak via shell history, process inspection, debug logs, crash reports, or misconfigured tooling, and a persistent dotfile increases the chance of accidental disclosure or insecure file permissions.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.