Threat intelligence · Annual service

Dark web monitoring and leaked credentials

Hard2bit, a Madrid-based cybersecurity company certified to Spain's ENS at High category, checks the dark web, Telegram cybercrime channels and data breaches every month for your staff's leaked credentials, access up for sale, impersonation of your brand and exposed information, each with its context and the recommended action.

Coverage
Dark web, Telegram and breaches
Frequency
Monthly review
Engagement
Annual contract

Who is accountable

Last reviewed: 2026-11-09

AI-generated background image

Hard2bit is certified to Spain's ENS at High category and to five ISO standards. The certificates are public and can be verified.

What is dark web monitoring and when does a company need it?

Dark web monitoring, also called leaked credential monitoring or dark web surveillance, is the regular review of dark web marketplaces and forums, cybercrime channels, data breaches and open sources to find a company's credentials, access or information that have leaked or are being sold. It lets organisations find them before anyone uses them, and show clients and auditors that this exposure is being watched.

Stolen credentials remain one of the main ways in: Verizon's Data Breach Investigations Report put them behind 22% of the breaches it reviewed in 2025 and 13% in 2026, second only to the exploitation of vulnerabilities. That's why we concentrate on dark web marketplaces and forums, where they're sold, and match them against breaches, cybercrime channels and open sources to catch what leaks by other routes. It's one part of what the market calls digital risk protection (DRP).

When organisations take it on

  • A breach at a supplier

    A third party you share data or access with has had an incident and you don't know what of yours left with it. In Verizon's 2026 DBIR, breaches involving a third party now account for 48% of the total.

  • Work email used outside the company

    Staff sign up to outside services with their work address. Every breach of those services exposes it and, where passwords are reused, the way into the company too.

  • Personal devices with corporate access

    A home laptop infected with an infostealer gives away company passwords and session cookies, which can be used to log in without passing the second factor.

  • Brand impersonation

    Lookalike domains, fake profiles or phishing campaigns that use your name against customers and staff.

  • Highly exposed executives

    Their accounts, and the personal data circulating about them, feed CEO fraud and access to sensitive information.

  • A client, insurer or auditor asks for it

    You need to show that credential exposure is monitored as part of how you manage risk.

  • After an incident

    Following an intrusion or a ransomware attack, you need to know what has been published on leak sites or is being sold.

Self-assessment

Is your company exposed on the dark web?

Tick whatever applies to your organisation today. Each one makes it more likely that company credentials or information are circulating outside your control, or raises the damage they can do if they are.

Signs of credential and information exposure

Result

Tick the signs that apply to your organisation.

Scope

What we watch: leaked credentials, access for sale, brand impersonation and data leaks

Scope is shaped around what each organisation needs to protect and can be extended during the contract.

  • Credentials and access

    Staff usernames and passwords in breaches, combolists and infostealer logs, stolen session cookies and corporate access put up for sale by brokers. Covers the executives and key people you name.

  • Suppliers and third parties

    Credentials and access belonging to suppliers you share systems or data with. Their exposure is a direct way in, and fits with third-party risk management.

  • Brand and domains

    Domains registered to impersonate you (typosquatting, homoglyphs or combinations with your brand), fake profiles and mentions tied to fraud campaigns.

  • Data leaks

    Internal documents, customer data, code or configuration published or offered for sale, with what you need to judge the impact.

Sources

Where we look: dark web, Telegram, breaches and stealer logs

Credentials and access sold today surface first on dark web marketplaces and forums and in cybercrime channels. Published breaches and open sources cover the rest. The ENISA Threat Landscape 2025, which analyses 4,875 incidents in Europe between July 2024 and June 2025, ranks phishing as the leading way in (60%), and the credentials it steals are the ones that end up for sale in these markets.

For broader intelligence on actors, campaigns and trends in your sector, the service plugs into our Threat Intelligence programme.

  1. 01

    Dark web marketplaces and forums

    Where credentials, corporate access and stolen data are bought and sold. The hardest source to cover, and the core of the service.

  2. 02

    Cybercrime channels and leak sites

    Telegram channels and communities trading access and infostealer logs, plus the leak sites where ransomware groups publish their victims' data.

  3. 03

    Breaches, combolists and stealer logs

    Public and private breach dumps, combined credential lists and infostealer logs, matched against your domains and assets.

  4. 04

    Open sources

    Code repositories, paste sites and the public web, where passwords, keys and documents leak by mistake or oversight.

How it works

How the service runs

Once we've established what's already exposed, the review repeats every month.

  1. 01

    Scope and proposal

    In a first meeting we agree what to watch: domains, brands, executives, critical suppliers and types of information. We then send the proposal. Scope can be extended during the contract.

  2. 02

    Initial sweep

    The first piece of work under the contract: a full review that establishes what of your organisation is already exposed and what to sort out before ongoing monitoring begins.

  3. 03

    Monthly review

    Every month we go back through every source looking for new exposure. If you need more intensive monitoring, the frequency is agreed in the contract.

  4. 04

    Verifying every finding

    Before reporting anything we check what's exposed, whose it is, how old it is and whether it's likely to still be valid, to rule out duplicates and false positives.

  5. 05

    Monthly report

    The month's findings go into the report, each with its priority and what to do about it.

Life of a finding

What happens when one of your credentials turns up

Every exposure follows the same path, from the moment it appears until someone confirms it has been dealt with.

  1. 1

    Detection

    Credential, access, domain or document

    • A credential in a breach or an infostealer log
    • Company access advertised on a forum
    • A new domain imitating yours
    • An internal document published
  2. 2

    Verification

    Who it affects and how much

    • Who it belongs to and which system it opens
    • Age and likely origin
    • Whether it's likely to still be valid
  3. 3

    Report

    What to do and how urgently

    • Priority based on real risk
    • A specific recommendation for each finding
    • Included in the monthly report
  4. 4

    Follow-up

    Until it's closed

    • Confirmation that action was taken
    • Rotation and containment where we run your SOC
    • Blocking recommendation for impersonating domains
    • Progress in the next report

Deliverables

What you receive: exposure reports and a profile for every finding

  • Baseline report

    The outcome of the initial sweep: everything of your organisation that is exposed today, prioritised by risk.

  • Monthly exposure report

    The month's new findings with severity, context and a recommended action for each.

  • Finding profile

    What's exposed, likely origin, age, whether it's likely to still be valid and the risk it poses.

  • Leadership summary

    Exposure level, month-on-month trend and outstanding decisions, in a short read.

  • One-off requests

    Answers outside the monthly cycle about a specific domain, brand or person. Reports in English or Spanish.

Team and assurance

Who does the work and what stands behind it

The service is led by Thilina Manana and run by the threat intelligence team; where we operate your SOC, containment is ours too.

  • Service leadership

    Thilina Manana, Director of Operations and Security and ISO 27001:2022 Lead Auditor (CQI IRCA), is accountable for the scope, the quality of findings and the confidentiality of the service.

  • Threat intelligence team

    Analysts who watch the dark web, cybercrime channels and breaches, and check every finding before it reaches the client.

  • SOC/MDR team

    Where Hard2bit runs the client's SOC or incident response, it acts on the findings: credential rotation, session revocation and access blocking.

Hard2bit is certified to Spain's ENS at High category (certificate ENS_2.026.061, issued by ACCM, a body accredited by ENAC under no. 48/C-PR503, valid until 20 April 2028) and to ISO 27001, 22301, 20000-1, 9001 and 14001. Findings are handled within our certified management system, audited every year by an accredited certification body. The service provides evidence for ISO 27001, ENS, NIS2 and DORA, and connects with our managed SOC and attack surface management.

Engagement

How it's contracted

It's an annual service with a monthly review, which can be stepped up to more intensive monitoring if you need it. We start with a meeting to set the scope and send you a proposal. The first piece of work under the contract is the initial sweep, which sets the baseline. Before starting we verify that the domain is yours: we only review domains for whoever controls them.

Request a proposal

What shapes the scope

  • Domains and brands being watched.
  • Executives and key people included.
  • Suppliers and third parties in scope.
  • Review frequency: monthly or more intensive.
  • Integration with Hard2bit's SOC or incident response.

Frequently asked questions

Common questions about dark web monitoring

How do I know if my company's credentials are on the dark web?

Through a sweep that matches your domains against the places where stolen credentials are sold and published: dark web marketplaces and forums, cybercrime channels, breaches and infostealer logs. The initial sweep, the first piece of work under the contract, shows what is already exposed. From then on, the monthly review picks up anything new.

Which companies in Spain and Europe offer dark web monitoring that supports NIS2, DORA or ENS evidence?

Hard2bit, a Madrid-based cybersecurity company certified to ENS High category (ENS_2.026.061) and ISO 27001, offers dark web monitoring as an annual service for organisations across Spain and Europe, including subsidiaries of international groups. It reviews dark web marketplaces and forums, cybercrime channels, breaches and open sources every month, and its reports serve as evidence for NIS2, DORA, ENS and ISO 27001.

We're the Spanish subsidiary of an international group: can the reports be in English?

Yes. Reports, finding profiles and the leadership summary can be delivered in English or Spanish, so the local team and group security can work from the same document. Scope can cover the subsidiary's own domains and brands, and meetings can be held in English.

We supply the Spanish public sector: which dark web monitoring provider holds ENS High certification?

Hard2bit is certified to ENS High category, the most demanding level of Spain's National Security Framework (certificate ENS_2.026.061, issued by ACCM and valid until 2028). Each client's findings are handled within that certified system, which makes it easier to fold the service into your own ENS compliance.

We're a financial entity under DORA: who monitors leaked credentials and access for sale as part of Article 13?

Article 13(1) of DORA requires financial entities to gather information on vulnerabilities and cyber threats. Dark web monitoring provides part of that information: credentials belonging to staff and ICT providers, access for sale and mentions of the entity, with a monthly report. Hard2bit delivers it from Madrid and ties it in with its DORA compliance service.

One of our suppliers has had a breach: how do we find out whether our credentials or data are on the dark web?

By including that supplier and your own domains in scope: we look for credentials, access and documents of yours that came out of the breach and assess whether they're likely to still be valid. Verizon's 2026 DBIR reports that breaches involving a third party rose by 60% and now make up 48% of the total. Third-party risk management covers the rest.

We've been hit by ransomware: who can watch whether our data is published or sold?

Ransomware groups publish the data of victims who don't pay on their leak sites, and that data then spreads to forums and sales channels. We watch those sources to establish what has been published and what is circulating, with a monthly report. If you also need to contain the incident, our incident response retainer handles that side.

How is this different from Have I Been Pwned or other free breach checkers?

Have I Been Pwned and similar services show whether an address appears in known, already published leaks. Monitoring also covers dark web marketplaces and forums and cybercrime channels, where recent credentials and access are sold. It repeats every month, spans domains, brands, executives and suppliers, and checks every finding before it's delivered.

We already have Microsoft Entra ID Protection: do we still need dark web monitoring?

Entra ID Protection flags leaked credentials for accounts in your tenant when Microsoft finds them. It doesn't cover access for sale, brand impersonation, exposed documents, or the credentials of your suppliers and of services outside Microsoft. The two complement each other, and the tenant side is covered by our Microsoft 365 security service.

What happens when a leaked credential turns up?

We check who it belongs to, which system it opens and whether it's likely to still be valid, and include it in the report with the recommended action: usually changing the password, revoking active sessions and reviewing the access. Where Hard2bit runs your SOC or incident response, rotation and containment are coordinated from there.

Does it count as evidence for ISO 27001, NIS2, DORA or ENS?

It provides evidence for a control. ISO 27001:2022 covers threat intelligence in Annex A control 5.7; the NIS2 Directive requires incident handling and supply chain security measures under Article 21(2), and DORA requires financial entities to gather information on vulnerabilities and cyber threats under Article 13(1). If we work with you on ISO 27001, ENS, NIS2 or DORA, the reports feed straight into that evidence.

If our customers' personal data turns up, do we have to notify the regulator?

That depends on the controller's assessment. Article 33 of the GDPR requires a personal data breach to be notified to the supervisory authority (in Spain, the AEPD) within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to individuals. The finding profile gives the date, scope and type of data for that assessment, which belongs to the controller and its data protection officer.

How do you choose a dark web monitoring provider?

Compare six things: whether it covers the dark web and cybercrime channels or only published breaches; whether it checks findings before delivering them; how often it reviews; whether scope includes executives and suppliers; whether findings are handled within a certified system such as ENS or ISO 27001; and whether it can act on them through a SOC or incident response service.

What's the difference between dark web monitoring, threat intelligence and digital risk protection?

Dark web monitoring looks for your organisation's credentials, access and information that have already leaked or are for sale. Threat intelligence analyses the actors, campaigns and trends targeting your sector, and is where early warning belongs. Digital risk protection is the market's name for the wider set of services that watch a company's external exposure, including the dark web and brand impersonation. This service can be taken on its own or as part of the threat intelligence programme.

How is it contracted and how often is it reviewed?

It's an annual contract with a monthly review, which can move to more intensive monitoring if you need it. It's sized by the domains, brands, executives and suppliers included. After the scoping meeting we send the proposal, and the initial sweep is the first piece of work under the contract. Reports are available in English or Spanish.

Concepts from our cybersecurity glossary that connect directly with this service.

Find out what of your company is exposed

We'll send you a proposal with the scope. Once you sign, the initial sweep shows your current exposure, and from there the review is monthly.

Reviewed by Thilina Manana and Hard2bit's threat intelligence team. Last reviewed: 2026-11-09.