Back to skill

Security audit

Paid Waitlist Page

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly coherent for deploying paid waitlist pages, but its trigger scope and setup instructions could lead to unintended hosted, metered infrastructure use.

Install only if you specifically want SettleMesh to deploy a live hosted waitlist or preorder page with managed persistence. Confirm before any deploy, payment, or billed action; prefer a pinned reviewed settlemesh CLI version and a least-privileged API key.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:35
Finding

Unpinned Global Installation of a Mutable Third-Party CLI

Content
View full analysis
Remediation
View remediation
``` 2. Publish and verify the expected npm package name, publisher identity, registry URL, version, and integrity hash through a trusted channel. 3. Prefer a project-local dependency with a committed lockfile over a global installation. Invoke it through a controlled package script or an equivalent mechanism that uses the locked version. 4. Install and execute the CLI using a dedicated, least-privileged account or isolated environment. Do not use `sudo` or an administrator shell. 5. Disable npm lifecycle scripts during installation if the package supports operation without them: ```bash npm install --ignore-scripts settlemesh@ ``` If lifecycle scripts are required, review them before installation and execute them only in a sandbox. 6. Do not immediately authenticate through a newly downloaded executable. Verify the installed package version and provenance first, then run authentication as a separate step. 7. Scope API keys to the minimum necessary permissions, avoid exposing them to unrelated processes, rotate them after suspected compromise, and protect cached sessions with restrictive filesystem permissions. 8. Establish an update process in which new CLI versions are reviewed and tested before changing the pinned version. ]]>
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (1)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The skill description is broad enough to trigger on generic requests for landing pages, signup forms, waitlists, or email capture, which can cause the agent to select a networked deployment skill that provisions infrastructure, persists user data, and may enable payments when the user only wanted simple content generation. In this context, the overbroad scope is more dangerous because the skill is explicitly capable of authenticated remote actions and resource creation, so a loose match can escalate a low-risk request into unintended external operations and billing.

Content

No source excerpt is available for this finding.