← Back to Hirdman
Compare us on your data
Hirdman · Data Leak Intelligence

One leaked record. The whole attack path, closed.

Breach monitoring, reverse checks, attack-surface reconnaissance and brand protection, carried out end to end by Hirdman analysts. You receive verified findings and a plan that is ready to act on.

1 to 2 days
to the first results after kickoff, often before the paperwork
Every hour
VIP accounts are checked: executives, administrators, engineers
106+ bn
records in the breach corpus, every source validated before it reaches you
300 to 500
new data points from one account in a reverse check, by our practice
What you receive

We take the work on ourselves.

Give us a domain. We search closed sources, verify every record, follow the links, rank the risk and tell you what to fix first. Nothing to configure and nothing to sort out on your side.

  • Every record verified: age, origin, and whether it is a repackaged old set or a generated one.
  • Every finding with a decision: fix now, fix this week, or safe to defer.
  • Confirmed risks reported at once through the channel you choose. The full report follows.
Raw feed, as vendors deliver it6 records
john.d@aceme.example : ********Tier 2 · corporate
john.d@aceme.example : ******** (second dump)duplicate
combo list, compilation of 201410+ years old
infostealer log: session cookie, VPN configTier 1 · now
admin : ******** (no e-mail)Tier 1 · now
"fresh 2025 breach", generated setgenerated, dropped
2Tier 1: fix now
1Tier 2: this week
3Noise removed

Six lines in, three decisions out. Each decision comes with the fix and the evidence.

Reverse check

From one record to every door it opens

Scroll to follow one breached login through the rounds our analysts run.

1

A breach lists one corporate login. The password was changed and the ticket closed. We take the identifiers out of the record: login, mailbox name, password pattern, unique domain.

2

Round one: the same mailbox name turns up on a personal address and at a previous employer.

3

Round two: a username that mutates by the same rule, and a shop registered with the work e-mail and the same password.

4

Round three: the shop's password opens the corporate portal, and an admin login without e-mail appears. This is the path a monitoring feed never shows.

5

Every link gets a fix and a priority: unique passwords, passkeys and a second factor on the portal, the admin account closed.

Full cycle

Every stage is ours.

Monitoring and penetration testing cover two different doors. We watch both, and we stay on a case until the fix is confirmed.

01CollectClosed forums, infostealer logs and private sources, early in the data lifecycle.
02VerifyAge, origin, duplicates. Generated and repackaged sets are filtered out.
03Reverse checkLinks across services, people and password patterns.
04ReconnaissanceDomains, subdomains, open services, shadow IT, mobile apps.
05PrioritizeRisk tiers weighted by account type, infostealer trace and password strength.
06NotifyConfirmed risks reported at once. VIP accounts checked every hour.
07Remediate and re-checkFixes verified. Nothing is left on your desk.
Services

Four practices, one team.

Offensive experience on every engagement: we look at your company the way an attacker does on day one, then close what we find.

Breach monitoring and brand protection

The full cycle from the previous section, as a service. Closed sources, verified records, reverse checks, risk tiers and immediate notification.

  • Lookalike domains and phishing sites, checked by evidence, not by spelling alone.
  • Fake mobile apps in third-party stores, taken apart to see what they change and where data goes.
  • Brand mentions in open and closed sources, including posts by former staff.
  • Takedown packages for registrars, app stores and lawyers: originals, hashes, timestamps, action log.

Penetration testing

External perimeter, internal network, web and API, mobile. A report with real attack paths, proof of each, and a fix list in priority order. Banks, oil and gas, public sector.

Code analysis and reverse engineering

Source review with commercial scanners and manual verification, binary and mobile-app internals, third-party software checked before rollout. Our engineers run reverse-engineering communities and work at machine-code level daily.

People Risk Management

Candidate screening within legal limits, insider-risk signals during employment, and monitoring after departure, when a former employee may still hold access or a grudge.

Your data stays with us

Own servers and own models. Client data never passes through public AI services or third-party clouds. The database is reachable from nowhere public.

What changes

Decisions instead of a dump.

We became clients of the services on the market and ran them on real data. This is where the outcome differs.

CriterionTypical outcomeWith Hirdman
Data quality
Unverified sets, often generated or repackaged.
Every source validated by analysts. Noise never reaches your cabinet.
Date of the breach
The upload date is shown as the breach date.
Source date and breach date kept apart, with a confidence level stated.
Prioritization
A list of records, sorted by the client.
Risk tiers with a decision for each finding: now, this week, can wait.
Notification
Weekly batches, then weeks of back-and-forth.
A confirmed risk is reported at once. VIP accounts are checked every hour.
Dark web
Public onion pages presented as closed sources.
Closed forums and private sources. Data taken early, before it is repackaged.
Scope and pricing
Per-asset licences, export limits, paid modules.
Scope agreed up front. No limits on the cabinet, exports or checks.
Who does the work
The client's team, from an alert.
Hirdman analysts, from the domain to the confirmed fix.
From a recent engagement

No leaked password on the domain. Keys to production in a public file.

During attack-surface reconnaissance we found a UI development tool on two of the client's subdomains. Its version compiled the environment file into the public bundle: tokens for repositories, cloud roles, databases and storage.

The domain had no leaked e-mails or passwords, so a monitoring feed would have shown nothing. The vulnerability is rated low by CVSS (3.1), yet the file held live keys. One token confirmed repository access. The client was notified at once and rotation of every secret started right after.

Published with the client's permission Company and domains anonymised
120+
environment variables in one public file, over 700 across all bundles. Readable by anyone who opened the page.
Next step

Compare us on your own data.

Already using a monitoring service? With your permission we run your data through our process and show the difference side by side. Free, with no obligation. If we show nothing new, you have had an independent check of your current vendor.