alby-hub

MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).

• Potentially malicious external URL detected (high risk: 1.00). The installation instructions explicitly run remote install scripts (e.g. /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/getAlby/hub/master/scripts/linux-x86_64/install.sh)" and /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/getAlby/hub/master/scripts/linux-aarch64/install.sh)" and /bin/bash -c "$(curl -fsSL https://getalby.com/install/hub/pi-aarch64-install.sh)"), which fetch and execute external code at runtime and are presented as required installation steps.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

• Direct money access detected (high risk: 1.00). Yes. The skill is explicitly designed to manage a Lightning/Bitcoin node and includes concrete commands and features that can move funds:
• "Payments: Pay/make invoices, transactions, lookup, balances, wallet address" — explicit send/pay capabilities.
• "Swaps: Swap on-chain bitcoin ↔ lightning (swap in / swap out)" — explicit on-chain/lightning asset movement.
• "Sub-wallets: ... transfer funds in/out, pay from a sub-wallet" — explicit fund transfers between wallets.
• "LSP: Order a channel up front" and channel open/close operations — actions that allocate or move liquidity.
• create-app returns a nostrWalletConnectUrl that "grants wallet access" (a connection secret that allows spending). Additionally, the JWT token file grants "full hub API access" which would permit executing those financial operations via the CLI/API.

These are specific, finance-oriented APIs and commands to send funds and perform swaps rather than generic tooling, so this qualifies as direct financial execution authority.