T03 · Remote Payload Retrieval and Execution
- Location
scripts/install.sh:48- Finding
Mutable Remote Code Installation Through Unpinned Latest Release
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent for using lnget, but it directs users toward real Lightning payments with overbroad node credentials and an unpinned remote install path.
Install only with a pinned, reviewed lnget version, avoid using an LND admin macaroon, prefer a least-privilege Lightning credential or limited wallet with low balance, use --no-pay and conservative --max-cost/--max-fee limits first, and periodically clear cached tokens and revoke unused LNC sessions.
scripts/install.sh:48Mutable Remote Code Installation Through Unpinned Latest Release
SKILL.md:157Use of LND Administrator Macaroon Violates Least Privilege
The skill explicitly describes automatic Lightning invoice payment and token reuse, but the introductory text does not prominently warn that using the tool can spend real funds and cache paid authorization tokens for future requests. In an agent context, that omission increases the risk of unintended micropayments and silent re-use of previously purchased access against remote services.
The Quick Start demonstrates fetching an L402-protected resource immediately after setup, which may cause automatic payment, but it provides no warning before the example. Because Quick Start snippets are the most likely to be copied verbatim, this materially increases the chance of accidental spending by users or autonomous agents.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
lnget config init
lnget --max-cost 1000 https://api.example.com/paid-data
## Installation
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
## Configuration File
Config lives at `~/.lnget/config.yaml`. Run `lnget config init` to create it.
**Note:** `lnget config init` may generate incorrect YAML key names (e.g.,
`tlscertpath` and `macaroonpath` instead of `tls_cert` and `macaroon`) due to
No suspicious patterns detected.