Back to skill

Security audit

Vacation Property Management

Security checks for vulnerabilities and agentic risk

Overview

The skill matches its TIDY property-management purpose, but it exposes long-lived credentials and live delete/update operations without enough user-control guidance.

Install only if you are comfortable giving the agent access to TIDY property, reservation, and access-note data. Protect TIDY_API_TOKEN like a password, prefer least-privileged or dedicated accounts, confirm before any delete/update action, and avoid the optional unpinned global CLI unless you trust and can verify that package source.

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:216
Finding

Unpinned Third-Party CLI Packages Installed Globally

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 216
Vulnerability Type: Unpinned and unverified third-party dependencies
Risk Level: Medium

Vulnerable Code

markdown
## CLI Alternative

Install: `brew install tidyapp/tap/tidy-request` or `npm i -g @tidydotcom/cli`.

Technical Analysis

The skill recommends installing third-party CLI packages from a Homebrew tap or the npm registry without pinning a reviewed version or verifying the downloaded artifact's checksum or signature. Both commands therefore resolve to whichever package release is current at installation time, allowing the installed implementation to change after this skill has been audited.

The npm command installs the package globally and may execute package lifecycle scripts under the invoking user's privileges. Because the package's source is not included in the audited project, its behavior—including installation hooks and handling of TIDY_API_TOKEN—cannot be verified from this artifact.

This creates a supply-chain trust boundary: compromise of the package publisher, registry account, npm package, Homebrew tap, or upstream distribution artifact could turn the documented installation command into a local code-execution vector.

Attack Path

  1. An attacker compromises the npm publisher account, Homebrew tap, upstream artifact, or another relevant distribution component.
  2. The attacker publishes a malicious release under the legitimate package name.
  3. A user follows the unpinned command in SKILL.md.
  4. The package manager retrieves the current compromised release because no version or digest is fixed.
  5. Malicious installation hooks or CLI code execute with the user's privileges.
  6. The payload can inspect user-accessible files and environment variables, potentially including TIDY_API_TOKEN.
  7. The stolen token may be used to perform authenticated TIDY API operations within the permissions granted to that token.

Impact Assessment

Successful expl ...[truncated 665 chars]

Remediation
View remediation

Remediation Suggestions

  1. Pin the CLI to a specific, reviewed version rather than installing the latest mutable release.
  2. Publish trusted SHA-256 checksums or cryptographic signatures and require verification before installation.
  3. Link to the CLI's verifiable source repository and document the reviewed source revision corresponding to the pinned release.
  4. Prefer a project-local installation over a global npm installation to limit scope and improve reproducibility.
  5. Use least-privileged accounts or isolated environments when installing and running third-party tools.
  6. Disable npm lifecycle scripts during installation when they are not required, and explicitly document any scripts that must run.
  7. Apply minimum necessary permissions to TIDY_API_TOKEN, keep it out of persistent shell configuration where practical, and rotate it immediately if package compromise is suspected.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The authentication section states that bearer tokens do not expire and shows exporting the token into an environment variable, but does not warn that these long-lived credentials must be protected like passwords. If exposed through shell history, logs, screenshots, or shared environments, an attacker could gain persistent API access to reservation data, property details, and operational controls.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

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

bash
# Sign up
curl -X POST https://public-api.tidy.com/api/v2/auth/signup \
  -H "Content-Type: application/json" \
  -d '{"first_name":"Jane","last_name":"Doe","email":"jane@example.com","password":"secret123"}'

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill documents DELETE operations for addresses and reservations without any warning, confirmation guidance, or note about irreversible effects. In an agentic context, this increases the chance that a user or autonomous workflow could remove live property or booking data unintentionally, causing operational disruption and possible financial loss.

Content

No source excerpt is available for this finding.