Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md node scripts/wallet-audit.mjs example --out ./wallet-audit-example --json
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a bounded, read-only wallet-audit helper that uses public Hyperliquid data and writes local evidence files, with no signer, trading action, credential access, or background persistence found.
Install only if you are comfortable sending the chosen public wallet address and time window to Hyperliquid's Info API and storing raw wallet-activity evidence locally. Treat generated capture and evidence files as sensitive financial metadata when sharing them.
Referenced artifact was not completely inspected
node scripts/wallet-audit.mjs example --out ./wallet-audit-example --json
Referenced artifact was not completely inspected
node scripts/wallet-audit.mjs example --out ./wallet-audit-example --json
Referenced artifact was not completely inspected
node scripts/wallet-audit.mjs example --out ./wallet-audit-example --json
Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.
1. Resolve account address, network, time window and output directory from the request or existing context. Ask only for a missing input that changes correctness. Read [data scope and API limits](references/data-contract.md) when choosing the window or interpreting coverage.
2. Capture sequential public `userRole`, `userAbstraction`, `clearinghouseState`, `spotClearinghouseState`, `frontendOpenOrders`, `userFillsByTime` and `userFunding` reads. The helper accepts only the two official network endpoints and the named read types. Page limits, timeout and response-byte limits bound the work.
3. Verify the request/response SHA256 manifest and deduplicate identical activity. Malformed numbers, unsafe identities, conflicting duplicates, wrong account/network and out-of-window records fail closed. An HTTP or network failure is retained as an explicit missing read. Do not treat it as zero activity or retry indefinitely.
4. Analyze default-perp closed PnL, signed fees/rebates and funding, maker/taker notional shares and per-market fee concentration. Fees retain their token denomination. `builderFee` is already included in `fee`; do not add it again. Non-USDC fees without valuation keep net USDC unavailable.
5. Separate current default-perp positions and spot balances from historical activity. Under unified or portfolio-margin accounts, spot balances are the trading-balance source. Do not add them to perpetual `accountValue`. Other DEX positions are outside this helper's exposure scope.
6. Return the observed outcome, largest supported cost or exposure finding, coverage status and files. State that API exhaustion does not prove a complete window. Report initial inventory from the first observed fill as an observation, not the window's opening position.
The fixture contains granular wallet activity, balances, open orders, fills, and funding records tied to a wallet address, which are sensitive financial data even if the address is public on-chain. Shipping this as an example without an explicit warning or minimization increases the chance that real captures are copied, shared, or logged in ways users may not expect.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Public read contract
Verified against the official Info documentation on 2026-10-09. Mainnet endpoint: `https://api.hyperliquid.xyz/info`. Testnet: `https://api.hyperliquid-testnet.xyz/info`. Every request is POST with `Content-Type: application/json`. No signing or authentication is used. Query the account being examined, not its API-agent address.
The five snapshot request bodies are:
No suspicious patterns detected.