Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Plan Your Trip — Itinerary Builder, Flight + Hotel Bundles, Day-by-Day Travel Planning

v3.2.0

Plan your entire trip with AI — flights, hotels, attractions, day-by-day itinerary. Tell me your destination, dates, and interests, I'll handle the rest. Als...

0· 40·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill is a trip planner and explicitly requires live data from a 'flyai' CLI — that aligns with its description (Fliggy-powered travel search). However, the skill package metadata declares no install steps or config paths while the runtime instructions require installing and using a third-party CLI, which should have been declared.
!
Instruction Scope
SKILL.md forces the agent to use only flyai CLI output and never rely on training data, instructs installing flyai-cli via npm if missing, and includes a runbook that may append logs to a local file (.flyai-execution-log.json). Those instructions cause network activity, global package installation, and local disk writes (possibly containing the raw user query and other PII) even though the skill metadata declared no config paths or persistence.
!
Install Mechanism
There is no install spec in the registry metadata, yet the runtime instructions mandate running 'npm i -g @fly-ai/flyai-cli' if the CLI is absent. Installing a global npm package at runtime is a moderate-to-high risk action (network download, execution privileges) and should be declared explicitly with provenance (homepage/repo or trusted release host).
Credentials
The skill requests no environment variables or credentials, which is proportionate to trip planning. However, the runbook instructs logging the raw user query and CLI results to disk which could capture sensitive personal data (names, travel dates, locations). That persistent logging is not reflected in the declared config or requirements.
!
Persistence & Privilege
always:false and no elevated privileges are declared, but the skill's instructions (global npm install and the runbook's optional file append to .flyai-execution-log.json) create persistent system changes and files. These actions increase persistence/privilege footprint without being surfaced in metadata.
What to consider before installing
What to consider before installing/using this skill: - The skill requires installing a third-party CLI package at runtime (npm i -g @fly-ai/flyai-cli). That downloads and executes code from the npm registry and modifies your system globally — only proceed if you trust the package and its publisher. Prefer manually installing and inspecting the package first. - The skill's files instruct the agent to append execution logs (including the raw user query and CLI call results) to .flyai-execution-log.json if filesystem writes are available. That log can contain personal data (destinations, dates, names). If you install or run this skill, check for and control where logs are written, or run in an isolated environment. - The registry metadata does not declare the install step or any config paths. Ask the publisher for the flyai-cli project homepage/repository, a signed release, or an official vendor statement (Fliggy/Alibaba) before trusting the package. - If you want to proceed safely: (1) review the npm package source repo and its recent releases, (2) install the CLI manually in a sandbox (container/VM) to observe behavior, (3) deny global installs on production machines, and (4) locate and inspect any .flyai-execution-log.json files and remove or secure them if they contain sensitive data. What would change this assessment: if the skill metadata included an explicit, verifiable install spec pointing to an official repo or release, or if the owner supplied a trustworthy homepage/repository for @fly-ai/flyai-cli and documented the exact log behavior and file paths, the concern level would be reduced.

Like a lobster shell, security has layers — review code before you run it.

latestvk971q3r7t4j03ramsxe0aeh5h584ry72

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments