Security audit

Booking.com — complete toolkit

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed travel-data API integration, with a normal API-key requirement but weak guidance around storing that key securely.

Install only if you want an agent to query StayingAPI for accommodation data. Prefer a sandbox key for evaluation, store live API keys in a credential manager or runtime secret store rather than plaintext profiles when possible, and be aware that live API calls may consume account credits.

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

Confidence: 93% confidence
Finding: The document explicitly instructs the user to persist `STAYINGAPI_KEY` so it survives across sessions, but it does not warn that shell profiles, plaintext env files, or agent-managed config may store credentials on disk where other users, processes, logs, backups, or future prompts could access them. In an agent-skill context, encouraging durable storage without secure-handling guidance increases the chance of secret leakage beyond the immediate task.

Static analysis

No suspicious patterns detected.