DefiLlamaInstall

Overview

The node provides access to DeFi security incident data ("hacks") from the DefiLlama API. Specifically, the "List Hacks" operation fetches a list of DeFi security incidents and hack data, including details such as the name of the incident, amount lost, date, and classification/type of the hack.

This node is beneficial for users who want to monitor or analyze historical security incidents in the DeFi ecosystem. For example, security researchers, analysts, or portfolio managers can use this node to track recent hacks, assess risk exposure, or generate reports on DeFi security trends.

Practical examples:

• Fetching the latest 20 DeFi hacks to review recent security breaches.
• Filtering and analyzing hack data to identify common attack vectors or vulnerable protocols.
• Integrating hack data into dashboards or alerts for real-time monitoring.

Properties

Note: For the "Hack" resource and "List Hacks" operation, only the "Max Results" field is relevant from the provided additional fields.

Output

The output is an array of JSON objects, each representing a DeFi security incident (hack) with various properties. The node formats some numeric values into human-readable strings (e.g., amounts formatted as currency, dates formatted as local date strings).

Typical fields in each hack object include:

• name: Name or title of the hack incident.
• amount: Numeric value representing the loss amount.
• amount_formatted: Human-readable formatted string of the loss amount (e.g., "$12.34M").
• date: Timestamp or date string of when the hack occurred.
• date_formatted: Localized date string representation.
• classification: Type or category of the hack (e.g., exploit type).
• _metadata: Metadata about the fetched data including resource, operation, and fetch timestamp.

If no data is found, the output contains a JSON object with a message indicating no data was found.

Dependencies

• Requires internet access to call the DefiLlama public API endpoint: https://api.llama.fi/hacks.
• Optionally supports using an API key credential if configured, which will be sent as a Bearer token in the Authorization header.
• Uses the Axios HTTP client library internally for API requests.

Troubleshooting

• No data returned: If the node returns "No data found," verify that the DefiLlama API is reachable and that there are indeed hack records available at the time of the request.
• API errors: Network issues or API downtime may cause errors. Check connectivity and retry later.
• Credential issues: If using an API key credential, ensure it is valid and correctly configured in n8n.
• Max Results limits: Setting "Max Results" above 100 will be ignored or capped by the node/API; keep within 1-100.

Links and References

• DefiLlama API documentation: https://defillama.com/docs/api
• DefiLlama Hacks data overview: https://defillama.com/hacks
• Axios HTTP client: https://axios-http.com/

This summary focuses exclusively on the "Hack" resource with the "List Hacks" operation as requested.