Back to skill

Security audit

Spraay Shopify Self-Host

Security checks for vulnerabilities and agentic risk

Overview

The skill provides a coherent self-hosting workflow, with disclosed credential use and wallet-confirmed payments, although its Git commands require care.

Use the reset-and-push sequence only on a fresh fork; preserve any existing work or deploy from a separate branch instead. Review the pinned application source before supplying credentials, use the recommended restricted database role, and check recipients, amounts, fees, and wallet prompts before confirming a test payment. This verdict does not certify the application's audit or contract security.

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
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
94% confidence
Finding

Cloning the app and checking out a deployment version can support the declared purpose. However, the subsequent force-push changes the remote repository's branch history rather than merely preparing a local deployment. The description does not disclose repository rollback or history rewriting. --force-with-lease guards against unexpected concurrent remote changes but does not eliminate the history-rewriting behavior. The supplied chunk does not establish what the specified commit contains.

Content

No source excerpt is available for this finding.

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
65% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

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

bash
   git clone https://github.com/<your-fork>/spraay-shopify.git
   cd spraay-shopify
   git reset --hard 3acf3b674a14500728c2607d8be937ad600887ad
   git push --force-with-lease

If the user prefers not to pin and instead deploys from the latest main, advise them to review the diff between the audited commit and HEAD (git diff 3acf3b6..HEAD) before deploying, since the code will have access to their Shopify secret and database credentials.

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
90% confidence
Finding

The actual command is --force-with-lease, which is safer than an unconditional force push but still permits replacing known remote history with the older pinned revision. This can displace customizations and disrupt collaborators or branch-triggered deployments; it is the same underlying issue as SQP-2, not evidence of malicious parameter injection.

Content

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

git clone https://github.com//spraay-shopify.git cd spraay-shopify git reset --hard 3acf3b674a14500728c2607d8be937ad600887ad git push --force-with-lease

text
If the user prefers not to pin and instead deploys from the latest `main`, advise them to review the diff between the audited commit and HEAD (`git diff 3acf3b6..HEAD`) before deploying, since the code will have access to their Shopify secret and database credentials.
3. Deploy: Railway → New Project → Deploy from GitHub repo → select the fork. The repo ships a `railway.json` and Dockerfile, so the build is automatic. Alternatively, the **Deploy on Railway** button in the README works — the template pre-prompts for every required env var, with PORT defaulted to 3000.

The pinning workflow force-updates the fork's default branch without warning that existing branch history may be displaced.

Medium
Category
Output Handling
Confidence
91% confidence
Finding

The workflow replaces the fork's default-branch history without warning that commits after the pinned revision will be removed from that branch. A newly created fork reduces the likelihood of losing merchant changes, but an existing or customized fork could lose its normal references to those changes; --force-with-lease protects against unexpected remote updates, not intentional removal of known history.

Content

No source excerpt is available for this finding.