How websites get attacked, in plain English

About 35 minutesYou need: your builder's notebook, adjoas-kitchen open in Cursor, and your live site open on your phone
This video is in the full courseGet the course to watch every video and read every lesson in full. GHS 399, paid once.Get the course · GHS 399
Video · 13:05
Goal

Explain the five common ways small websites get attacked (bots and spam, leaked keys, open databases, weak logins and outdated packages), find each one on a map of your own app, and know which lesson in this module closes it.

Why this matters

When people imagine a website being "hacked", they picture a genius in a dark room typing fast, targeting one company. That does happen, to banks and governments. It almost never happens to a restaurant in Osu or a salon in Manchester.

What does happen to small sites is far more boring, and far more common. Programs called bots visit millions of websites a day, trying the same few tricks on every one. They don't know or care whose site it is. They fill in every form they find. They try common passwords on every login page. They search GitHub for keys that someone pushed by mistake. They check whether a site's database answers questions it shouldn't.

That's actually good news. Because the attacks are the same few tricks, the defences are a short, known list. You can learn that list in one module and apply it to every site you ever build. This lesson is the map. The rest of the module is the walk-round, door by door.

In the full lesson

  1. The idea in plain English
  2. Try it
  3. Check it worked
  4. Quick check
  5. What you can do now
Stage 2 · Make it workYou’ve seen the why. The how is in the course.

The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.

Get the course · GHS 399See what’s inside
Already have the course? Open the full lesson