What happens when a routine email confirmation becomes an attack tool? Charlie Forêt describes how bots used his Phoenix LiveView newsletter form to send unwanted confirmations, while corporate mail scanners accidentally confirmed some subscriptions by fetching the links. The traffic spike exposed more than a spam problem: the app trusted the wrong forwarded-IP header, kept rate limits only in ETS, and logged too little to make security events visible in production.
Forêt details the fixes, including moving confirmation actions behind a button, adding durable per-address and site-wide email caps, separating suppressed addresses from unsubscribed ones, and recording privacy-conscious security logs. He also explains how to pass Fly.io’s trusted client IP into LiveView and prevent password limits from locking out the administrator. The bots still send a trickle of sign-ups, but the new safeguards keep them within bounds—and stop scanners from confirming anyone.
continue reading onintegrationera.com
⚠️ This post links to an external website. ⚠️
If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.