Michael O'Brien ยท

The deferred maintenance on your website just came due

Being a small target used to be a defense. Now that an AI agent can try one more site for the price of compute, the plugin a version behind is the thing an attacker finds first.

At Uber, I designed, built, and owned account-takeover response for North America. Fraud work teaches you the old joke about the bear early. You don't have to outrun the bear, only the person next to you. A fraud ring has a list of targets and a limited number of hours, so it goes where the next account is cheapest to take, and a company only had to be a little harder to break into than the one beside it.

That logic depended on the attacker's time being scarce, and AI agents have made it cheap.

What changed this year

An AI agent can read a plugin's security notice, find the sites still running the old version, try the logins, and publish a page on each one it gets into. The work that used to take a person an afternoon per site now costs about what the compute costs, so the attacker stops choosing between targets and tries all of them. The bear is chasing every camper at once, and it catches each one who is slower than the bear, whoever is standing next to them.

For a small company, that removes the defense of being too small to bother with. A site with a few hundred visitors a month and a contact form gets the same attempts as a large one, because trying it costs the attacker almost nothing.

Who is slowest

The companies most exposed have fewer than forty people and no IT staff. The website runs on WordPress with a page-builder theme and twenty-odd plugins, built by a contractor who has since moved on. A HubSpot consultant connected the CRM through a plugin and a private app. The founder is the Google Workspace admin, and the domain renews on someone's personal card.

Each of those systems was set up well by the person who owned it, and the gaps sit between them. The contractor's admin login is still on the site, the plugin's access token has not been changed since it was connected, and the list of who can log in to what is spread across four people's inboxes. An attacker who gets into the website starts with exactly those gaps.

The bill for the updates you skipped

Every plugin left a version behind and every login kept for someone who finished in 2023 was maintenance put off for a good reason, because it cost nothing at the time. Breaking into a small company's site by hand took too long to be worth it. That cost has fallen far enough that the deferred work now has a price, and it arrives as a defaced page, spam sent from your domain, or a HubSpot form that sends your leads somewhere else.

Paying it down this quarter comes to five jobs.

  • List every login across the website, the host, the CRM, email, and the domain registrar, and remove the ones that belong to people who have left.
  • Turn on two-factor sign-in everywhere it exists, starting with the mailbox that can reset every other password.
  • Delete each plugin and theme you don't use, and update the rest. A plugin that is switched off can still be attacked while its files sit on the server.
  • Make sure the site can send mail, so a password reset reaches the person who asked for it.
  • Write down which system holds which key, and when each was last changed.

The website security check does those five jobs in one to two weeks, with the updates made on a safe copy before the live site.

Fewer dependencies, newer code

Some sites are past patching. A page-builder theme ties every page to one vendor's release schedule, and twenty plugins mean twenty projects that each have to keep up. Moving to a smaller stack is the larger fix: a static site, or a modern framework with a short dependency list, and HubSpot's own hosted forms in place of a plugin that stores an access token. This site is static HTML on Cloudflare, so it has no login page to guess and no plugin to update.

That trade costs something. WordPress lets your marketing team publish without a developer, and a static site gives some of that up for a much smaller surface to defend. If the site changes weekly, I'd keep WordPress and cut it down to what you use. If it changes a few times a year, I'd move.

For the consultants who set these up

If you're the HubSpot consultant or the web contractor, your admin logins reach every client you manage, which makes your accounts worth more to an attacker than any one client's. Put two-factor on each of them, keep one list of where you still have access, and hand access back when an engagement ends. Your clients will call you first when something breaks, so the list is worth having before that call.

If it has already happened

Keep the evidence before deleting anything, rule out access to the CRM, the mailbox, and the domain, and then close every way in during one session, in an order that leaves no second door. The account security cleanup runs in that order.

Next step

When did someone last remove a login from your website?

If you can't say, bring the users screen to a 30-minute call, and you'll leave with the first accounts to close.