Most breaches don’t start with a clever attack. They start with a password that was already for sale.

An employee’s laptop gets infected, or a service they signed up for gets breached, and their work login ends up in a dump online — often months before anyone uses it. By the time the intrusion happens, the credential had been sitting there the whole time.

I monitor for exactly that — your team’s leaked passwords and stolen session cookies, across both infostealer logs and breach data, continuously — and I do the part that actually matters: reading what turns up and telling you what to do about it.

Get a free exposure check →    Book a 20-minute call


Stolen logins come before the breach

The pattern is consistent and well-documented. In Verizon’s breach research, a large share of ransomware victims had their domain show up in infostealer logs or credential dumps before the attack — typically with a window of weeks to months in between.

Two ways it happens, and neither takes a sophisticated attacker:

  • An employee’s computer gets infected. Malware copies every password and login session saved in their browser — Microsoft 365, the bank portal, your admin tools. Including home laptops you never see.
  • Someone else gets breached. An employee reused their work password on a supplier portal or an online store. That company gets breached, the list leaks, and attackers try every pair against your systems. One reused password is enough.

Both end the same way: a working login to your environment, on sale, with nobody at your company aware.

What I monitor

You give me a domain. I watch it continuously across two sources:

  • Infostealer logs — passwords and live session cookies copied off infected machines. These often still work, and they name the exact service.
  • Breach data — the leaked email/password records from other companies’ breaches, checked against every address on your domain.

Every address on the domain is covered automatically — the new hire, the forgotten shared inbox, the account someone made in 2012. No employee lists to maintain, nothing to install.

What you actually get (the difference)

Anyone can buy raw alerts. The value is in what happens after a hit.

When something turns up, the alert comes to me first. I verify it, work out how serious it is, and send you a plain-language report: what leaked, which accounts, how exposed you are, and the specific steps to close it — reset this, revoke that session, check for this sign-in. You get a security advisor interpreting the finding, not a scary automated email landing cold in your inbox.

A stolen session is worse than a stolen password, because it can walk straight past MFA — so when one shows up, acting fast matters, and that’s what you’re paying for.

How it works

  1. Free exposure check. Send me your domain and I’ll run a one-time scan — no cost, no obligation. You see your current exposure before deciding anything.
  2. Continuous monitoring. If you move forward, I put the domain under 24/7 monitoring.
  3. Alerts, interpreted. New exposure is triaged by me and delivered as a clear report with remediation steps.
  4. Ongoing. You get a regular summary plus real-time alerts for anything critical.

Who it’s for

  • Startups and SMBs without a dedicated security team or SOC.
  • Teams on Microsoft 365 / Google Workspace where one leaked login opens the whole environment.
  • Anyone preparing for an audit or a security review who needs to show credential exposure is being watched.

If you already have a mature SOC running this in-house, you don’t need me.

Pricing

Simple and per-domain — a whole company covered by one domain, regardless of headcount:

MonthlyAnnual
Per monitored domain€149 / month€1,490 / year (2 months free)

Includes continuous monitoring, triaged alerts, and remediation guidance. No per-user fees, no minimums, no long contract. Multi-domain and bundled-with-audit pricing available on request.

(Pricing provisional — final figures confirmed at launch.)

Common questions

Do you ever see or touch our real passwords? No. The service only finds credentials that have already leaked publicly. I never log into anything, and the data is never used to access an account — it’s alert-only.

Where’s the data handled? Is this GDPR-compliant? Yes. You’re the data controller; I act as your processor under a data-processing agreement, with the monitoring platform as sub-processor. I’ll walk you through the specifics before you sign.

How is this different from a free breach checker? Free tools give you a raw list and stop there. You’re paying for the infostealer-log coverage (which free checkers don’t have), continuous monitoring, and — most importantly — me reading the findings and telling you exactly what to do.

We already enforce MFA. Do we still need this? Yes. Stolen session cookies bypass MFA entirely — the attacker reuses an already-authenticated session. Catching the leak early is how you stay ahead of that.


See your exposure, free

The fastest way to know if this is worth it is to look. Send me your domain and I’ll run a free exposure check — you’ll see exactly what’s out there before deciding anything.

Get your free exposure check →    Book a 20-minute call