Back to skill

Security audit

Shipyard setup

Security checks for vulnerabilities and agentic risk

Overview

The skill describes a coherent Shipyard account-setup process with disclosed permissions and user approvals, but its required plugin scripts are outside this review.

Use this for explicit Shipyard setup and review the full plugin before supplying credentials. The Supabase token covers all your projects, and the optional Resend key has full access. Keep keys out of chat, prefer a pinned Playwright version, and review proposed global instructions before accepting them. This assessment covers the three supplied documentation files, not the external plugin implementation.

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

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
## Rules (always)

- You do the work. Run the scripts and commands yourself. The student only clicks in a browser, signs up, and pastes keys into the keys file.
- Never ask the student to paste a key in the chat. Never read or print `~/.shipyard/secrets.env`. Only scripts read it, and they show names with a tick or a cross, never values.
- Plain English. Short steps. Say what to click and what URL to open. Explain any technical word in a few words.
- One question at a time. Tell them which answer you recommend.
- Check each step before moving on. Do not say "done" until the check passes.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
They sign up at vercel.com with "Continue with GitHub". Run `npx --yes vercel@64.3.1 login` (it opens a browser). Check with `npx --yes vercel@64.3.1 whoami`. Save `accounts.vercel.user`, `accounts.vercel.scope` (their team name if shown, otherwise the user name) and `accounts.vercel.ok true`.

**4. `supabase`** Why: Supabase holds the database and sign-in.
Sign up at supabase.com with GitHub. Create an access token at supabase.com/dashboard/account/tokens (any name). Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/secrets-init.mjs"`. It opens the keys file. They paste the token after `SUPABASE_ACCESS_TOKEN=`, save, close, and say "done". Then run `node "${CLAUDE_PLUGIN_ROOT}/scripts/secrets-check.mjs" --live`. When it shows a tick, find their organisation (the check output or the Supabase dashboard shows it; if there is only one, use it). Save `accounts.supabase.orgId` (the organisation's slug, the short name in the dashboard URL), `accounts.supabase.orgName` and `accounts.supabase.ok true`.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/troubleshooting.md (reported line 16)May include surrounding context.

md
| `vercel whoami` says no credentials | Login did not finish. Run login again |
| `secrets-check` says the Supabase token is missing | Open the keys file again with `secrets-init.mjs`. The line must be `SUPABASE_ACCESS_TOKEN=sbp_...` with no spaces, quotes or line breaks. Save the file |
| Token looks right but `--live` fails with 401 | The token was revoked or copied incompletely. Generate a new one and replace the whole line |
| Keys file opened in the wrong program | Open `~/.shipyard/secrets.env` (Windows: `%USERPROFILE%\.shipyard\secrets.env`) with any text editor |
| Playwright download fails | Check the internet connection and run `npx playwright install chromium` again. Phone-size checks are skipped until it works; apps still build |
| They pasted a key in the chat by mistake | Tell them to revoke that key in the provider's dashboard and make a new one, then paste it into the keys file only |
| Windows: script cannot run | Use the terminal Claude Code runs in. Do not run Shipya

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/troubleshooting.md (reported line 16)May include surrounding context.

md
ogin did not finish. Run login again |
| `secrets-check` says the Supabase token is missing | Open the keys file again with `secrets-init.mjs`. The line must be `SUPABASE_ACCESS_TOKEN=sbp_...` with no spaces, quotes or line breaks. Save the file |
| Token looks right but `--live` fails with 401 | The token was revoked or copied incompletely. Generate a new one and replace the whole line |
| Keys file opened in the wrong program | Open `~/.shipyard/secrets.env` (Windows: `%USERPROFILE%\.shipyard\secrets.env`) with any text editor |
| Playwright download fails | Check the internet connection and run `npx playwright install chromium` again. Phone-size checks are skipped until it works; apps still build |
| They pasted a key in the chat by mistake | Tell them to revoke that key in the provider's dashboard and make a new one, then paste it into the keys file only |
| Windows: script cannot run | Use the terminal Claude Code runs in. Do not run Shipyard scripts from an old Command Prompt tha

Activation phrases such as "setup", "get started", and "settings" are too broad without an explicit Shipyard-only invocation constraint.

Medium
Category
Trigger Abuse
Confidence
94% confidence
Finding

Generic activation phrases can route unrelated setup or settings requests into this account-provisioning workflow. Because the workflow immediately directs command execution without first confirming Shipyard-specific intent, accidental activation can cause unintended local execution and authentication prompts, although browser approval still limits account access.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx playwright'.

Medium
Category
MCP Rug Pull
Confidence
95% confidence
Finding

This is a Playwright CLI command, not an MCP server, but the unpinned execution risk is real. If Playwright is not installed locally, npx can fetch and execute the current registry version; a compromised release would run with the user's permissions on a machine holding cloud credentials.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx playwright'.

Medium
Category
MCP Rug Pull
Confidence
95% confidence
Finding

Although this command invokes a CLI rather than an MCP server, it does not constrain the Playwright version. When no local installation exists, npx can download and execute a current registry release, exposing the user's machine to a compromised upstream release during setup.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx playwright'.

Medium
Category
MCP Rug Pull
Confidence
95% confidence
Finding

The troubleshooting command repeats an unpinned executable dependency, not an MCP server reference. If a local Playwright package is absent, npx can obtain and execute the current registry release, allowing a compromised release to run with the user's privileges.

Content

No source excerpt is available for this finding.