TLDR
Aerodrome Finance and Velodrome Finance are the decentralized exchanges that publicly warned of DNS hijacking this week.
- Aerodrome urged users to avoid its main domains and use ethereum-name-service/">ENS mirrors, noting contracts were secure on X.
- Velodrome issued parallel domain security warnings during the same incident, per a credible news recap here.
Deep Dive
1. Aerodromes Warning
Aerodrome Finance reported a suspected DNS hijack and told users not to use its primary domain while they investigated. They later said centralized domains remained compromised and pointed users to ENS-based mirrors, while stating core smart contracts were secure.
- Initial alert to avoid the primary domain as they investigated a potential DNS hijack on X.
- Follow-up that centralized domains were still compromised and two decentralized ENS mirrors were safe to use on X.
- Reminder of approved ENS mirrors during migration and an incident thread for context on X.
If you interacted with Aerodrome via a centralized domain during the window, review approvals and wallet activity, and only access via the mirrors listed in the notice above.
2. Velodromes Parallel Alert
Coverage of the incident noted that Velodrome Finance, Aerodromes sister protocol, faced similar threats and issued parallel warnings about domain security.
- The same incident cycle flagged sister protocol Velodrome with similar domain threats and warnings, per this recap news article.
- Reports described the coordinated nature of warnings, suggesting multiple DeFi front ends were targeted at the domain layer in the article above.
- Aerodrome also suggested a domain provider issue during the episode on X.
Even if a DEXs contracts are safe, a hijacked domain can present malicious prompts. Access official links from verified posts and favor ENS or bookmarked mirrors.
Conclusion
The DEXs that publicly warned of DNS hijacking this week were Aerodrome Finance and Velodrome Finance. The practical takeaway is to distrust compromised centralized domains, verify official incident posts, and use the ENS mirrors referenced in the notices above until teams confirm restoration.
