How we stopped a brute-force attack on our own website

Manu Francis, cybersecurity trainer at Edwhere Learning

It started with a one-second lag

A while ago, logging in to our own website, edwhere.com, became slightly slow. Nothing dramatic: it just took about a second longer than usual. But our users log in every day, so they noticed straight away.

So we did the obvious thing: we opened the website's activity log and looked at what was actually happening.

What the logs showed

We were shocked. People from many different IP addresses were trying to log in to our system. Not once or twice, but 500, 600 and more attempts.

This is called a brute-force attack. Think of a thief who turns up with a thousand keys and tries each one in the lock, one after another, hoping one fits. Here the keys are passwords, and the lock is the login page. Spreading the attempts across many IP addresses makes the attack harder to block by simply banning one address.

  • ~1 secExtra login delay
  • 500–600+Login attempts
  • ManySource IP addresses
  • 3Defences we added

What we did about it

  1. Blocked admin logins from abroad Our admins are in India, so logins to admin accounts from other countries are now refused outright.
  2. Limited logins by time Admin logins are only allowed during the hours we actually need them.
  3. Hid the login page The admin login page now only opens when someone needs admin access. The rest of the time, the page simply isn't there.

The result: the thief can't even find the lock, let alone try keys in it. We're deliberately not sharing the exact settings, because that would only help the next attacker.

If you run a website, check these

  • Read your logs now and then. Failed logins pile up quietly. A small slowdown can be the only visible sign.
  • Limit failed attempts. Lock or slow down logins after a few wrong passwords.
  • Restrict admin access by country, time or network if your admins are in a known place.
  • Use long, unique passwords and two-factor authentication on every admin account, so a guessed password alone isn't enough.
  • Don't advertise the admin login. If only your team needs it, it doesn't need to be public all the time.

This is what a SOC does

Notice something odd, look at the logs, work out that it's an attack, and stop it. Thousands of people around the world do this work every day in a Security Operations Centre (SOC). It's the defence side of cybersecurity, and it's where most cybersecurity jobs are. See the SOC analyst career path, from L1 to manager.

Learn to do this yourself

Certified SOC Analyst (CSA) training

Build a real SOC on Wazuh, catch attacks like this one and stop them. 3 months, EC-Council's official exam voucher included, ₹32,000. Next offline batch in Aluva, Kochi: second week of January 2027.

See the CSA course WhatsApp "CSA" ›

Keep reading

Frequently asked questions

What is a brute-force attack?

An attack where someone tries password after password on a login page until one works, like a thief trying a thousand keys in a lock. Attackers often spread the attempts across many IP addresses.

How do I know if my website is under a brute-force attack?

Check your login or activity logs for large numbers of failed logins, especially from many IP addresses. A slowdown at login can be the first visible sign.

How do you stop a brute-force attack?

Limit failed attempts, restrict admin logins by country or time, hide the admin login page when it isn't needed, and use long unique passwords with two-factor authentication.

Who handles attacks like this in a company?

The Security Operations Centre (SOC). SOC analysts watch logs in a SIEM, spot attacks, investigate them and stop them.

Learn with Edwhere.

Hands-on courses in cybersecurity, IoT and programming, taught in Malayalam.