Cabin Flights
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: cabin Version: 1.0.0 The skill is classified as suspicious due to its instruction to the AI agent to perform a real-world cryptocurrency transaction. The `SKILL.md` file explicitly includes a command `node src/send.js base USDC <deposit_address> <amount_usdc> --yes --json` for sending USDC on the Base network. While this capability is plausibly needed for the stated purpose of 'USDC payments' and is conditional on the agent having 'wallet capabilities', it represents a high-risk operation involving shell command execution and financial transactions, without the `src/send.js` script being part of this skill bundle for direct analysis. There is no clear evidence of intentional malicious behavior, but the inherent risk of instructing an agent to execute such a powerful, external financial command warrants a 'suspicious' classification.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If an agent with wallet capability follows this path too aggressively, it could send USDC to a booking deposit address and create an irreversible payment the user did not intend.
This is a high-impact crypto payment command, and the --yes flag can suppress an interactive confirmation; the skill does not clearly require explicit final user approval immediately before sending funds.
node src/send.js base USDC <deposit_address> <amount_usdc> --yes --json
Require an explicit final user confirmation for the exact flight, passenger names, amount, chain, token, and deposit address; avoid --yes by default and use wallet spending limits.
The command may fail, run an unintended local script, or rely on an unreviewed external wallet skill when handling real funds.
The skill references local Node helper scripts for wallet balance and payment, but the provided package is instruction-only and does not include those src files, making the code provenance unclear for a funds-moving workflow.
node src/balance.js base --json # Send USDC to deposit address node src/send.js base USDC <deposit_address> <amount_usdc> --yes --json
Declare and pin the wallet dependency or call a named, reviewed wallet tool instead of unqualified relative scripts; include clear provenance and user-approval requirements.
Connecting a wallet gives the agent potential access to view balances and initiate payments for travel purchases.
The skill may use delegated wallet authority to inspect balances and send USDC; that is purpose-aligned for crypto flight payment, but it is sensitive account authority.
If the agent has wallet capabilities (e.g., evm-wallet skill): # Check USDC balance on Base node src/balance.js base --json # Send USDC to deposit address
Use a dedicated low-balance wallet, set spending limits where possible, and require manual approval for every payment.