Back to skill

Security audit

google-hotels-search

Security checks across malware telemetry and agentic risk

Overview

This skill is a coherent Google Hotels search integration that needs a StayingAPI key and internet access, with only a credential-storage caution for users.

Before installing, be aware that searches and account checks go to StayingAPI over the network. Use the sandbox key for evaluation where possible, store any live API key only in a private secret store or permissions-restricted user config, and avoid committing it to project files or exposing it to logs.

SkillSpector

By NVIDIA
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
90% confidence
Finding
The guide instructs users to persist the `STAYINGAPI_KEY` across future sessions but does not warn that shell profiles, shared env files, or agent-managed config can expose secrets to other local users, child processes, logs, backups, or version-controlled files. Because this is credential-handling documentation for an API key, omission of secure-storage guidance can lead to unintended disclosure and unauthorized use of the account.

VirusTotal

51/51 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.