For the complete documentation index, see llms.txt. This page is also available as Markdown.

Otomato for Security Alerts

With security alerts, we want to make sure you know it first when a protocol you are exposed to is compromised.

What we monitor

Otomato detects security threats affecting your positions through two layers of monitoring:

Social monitoring (today)

  • Protocol X accounts: If a protocol you use tweets about an incident, you're notified immediately

  • Security researchers: We track X accounts like Lookonchain, PeckShieldAlert, CertiKAlert, and other trusted sources who often break news first.

On-chain monitoring (coming soon)

  • Real-time transaction analysis: We monitor activity on protocols you're exposed to and detect suspicious patterns before anyone raises the alarm on X

Use cases

Hack or exploit detected

When a protocol you're exposed to is compromised, every minute counts. Otomato surfaces credible hack reports from protocol announcements and security researchers so you can assess whether to withdraw.

Example notifications

  • "Security incident reported on Euler Finance. View source."

  • "Aave tweeted about a potential exploit on their v3 markets. View source."

  • "Lookonchain flagged suspicious outflows from Curve pools. View source."

Frontend compromise

A compromised frontend can drain your wallet even if the protocol's smart contracts are safe. Otomato alerts you immediately when a protocol reports their website has been compromised.

Example notifications

  • "Balancer reported their frontend has been compromised. View source."

  • "Galxe's website is flagged as compromised. View source."

Improvements

We're continuously looking to add support for alerts the community is asking for. If you'd like us to add a new use case, reach out on Telegram.

Last updated