Skills lifi Audit History
πŸ“¦

Audit History

lifi - 2 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v2 LatestJul 19, 2026, 10:48 AM 2 confirmed14No capability change
v1 Jul 9, 2026, 11:41 PM No confirmed findings0Baseline

Jul 19, 2026, 10:48 AM

Of 147 static findings, 133 are false positives caused by Markdown formatting, placeholders, API terms, or non-executing endpoint references. Fourteen findings confirm intended outbound calls to LI.FI services, while two semantic findings identify high-risk transaction and vault-selection workflows. No prompt injection attempt was found.

2
Files scanned
1,472
Lines analyzed
19
Review items
0
False positives ignored

Confirmed security concerns (2)

High
Asset-moving workflow lacks mandatory user confirmation
The skill directs agents to approve, sign, and send transactions without requiring explicit confirmation of chain, tokens, amount, recipient, spender, fees, and slippage.
The documented canonical flow explicitly says to approve, sign, and send transactionRequest. No mandatory pre-signing user confirmation or complete transaction review is specified.
High
Yield example automatically selects the highest-APY vault
The Node.js example selects the first APY-sorted vault for a deposit quote without validating protocol risk, TVL, timelocks, caps, KYC, or user preference.
The example requests vaults sorted by APY and directly uses vaults[0].address as the deposit target. The shown code contains no risk filter or user selection step.
Capability review items (14)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low
Hardcoded URL Β· 4 occurrences
curl "https://li.quest/v1/quote?\
This executable curl example sends a request to an external LI.FI service. The call is expected, but it discloses supplied query data and trusts a third-party response.
Low
Hardcoded URL
curl "https://li.quest/v1/chains?chainTypes=EVM,SVM,UTXO,MVM,TVM"
This executable curl example sends a request to an external LI.FI service. The call is expected, but it discloses supplied query data and trusts a third-party response.
Low
Hardcoded URL
curl "https://li.quest/v1/tokens?chains=1,8453&tags=stablecoin"
This executable curl example sends a request to an external LI.FI service. The call is expected, but it discloses supplied query data and trusts a third-party response.
Low
Fetch API call
const res = await fetch(`${BASE_URL}/quote?${new URLSearchParams(params)}`);
The sample performs an outbound quote request to LI.FI with wallet and routing parameters. This intended call exposes transaction metadata to a third-party service.
Low
Fetch API call
const data = await (await fetch(`${BASE_URL}/status?${params}`)).json();
The sample sends a transaction hash and routing context to LI.FI for status tracking. This is intended functionality, but it discloses transaction metadata externally.
Low
Fetch API call
const { data: vaults } = await (await fetch(
The sample performs an outbound request to the LI.FI Earn service for vault data. It is read-only, but depends on untrusted third-party network data.
Low
Python HTTP libraries
r = requests.get(f"{BASE_URL}/quote", params=params, headers=HEADERS)
The sample performs an outbound quote request to LI.FI with wallet and routing parameters. This intended call exposes transaction metadata to a third-party service.
Low
Python HTTP libraries
return requests.get(f"{BASE_URL}/status", params=params, headers=HEADERS).json()
The sample sends a transaction hash and routing context to LI.FI for status tracking. This is intended functionality, but it discloses transaction metadata externally.
Low
Hardcoded URL
curl "https://li.quest/v1/chains" -H "x-lifi-api-key: YOUR_API_KEY"
This executable curl example sends a request to an external LI.FI service. The call is expected, but it discloses supplied query data and trusts a third-party response.
Low
Hardcoded URL
curl "https://li.quest/v1/status?txHash=0xYourTxHash&fromChain=42161&toChain=10&bridge=across"
This executable curl example sends a request to an external LI.FI service. The call is expected, but it discloses supplied query data and trusts a third-party response.
Low
Hardcoded URL
curl "https://earn.li.fi/v1/vaults?chainId=8453&asset=USDC&sortBy=apy&isComposerSupported=true&limit
This executable curl example sends a request to an external LI.FI service. The call is expected, but it discloses supplied query data and trusts a third-party response.
Audited by: codex

Jul 9, 2026, 11:41 PM

All 147 static findings were adjudicated as false positives. The flagged URLs, HTTP examples, API key strings, and backticks are documented LI.FI API examples or Markdown syntax, with no hidden execution, credential access, local reconnaissance, or prompt injection found.

2
Files scanned
1,480
Lines analyzed
3
Review items
0
False positives ignored
Audited by: codex