Brand Monitoring and Dark Web Monitoring Services | ThreatDefence
Skip to content

Brand Monitoring

ThreatDefence brand monitoring finds look-alike domains, cloned websites, fake apps and accounts, leaked code and secrets, and stolen credentials linked to your organization. The Brand monitor agent searches for misuse across public and criminal sources, while ThreatDefence’s 24x7 SOC confirms significant findings, coordinates credential and key closure, and manages takedowns under your approval.

The Brand monitor for acme-corp this week: a findings feed on the left and a map of every finding on the right, from a cloned login page and an API key in a public code repository to an exposed remote desktop server, a negative social media post, a repackaged app, a Telegram channel and a stealer logTakedown of the cloned login page on acmec0rp.com: found and blocked, approved by acme-corp and taken offlineThis week for acme-corp: two live threats, two leaked secrets closed, three fakes reported and one source under watch

Where Brand Monitoring Looks

The Brand monitor searches outside your network for misuse of the brands, domains, products, people, and accounts you choose to protect. Its watch lists cover new registrations, public content, impersonation attempts, and exposed data across multiple sources.

Domain registrations

The agent checks new registrations daily, together with DNS, WHOIS records, and certificate transparency logs.

Public code repositories

GitHub, GitLab, public gists, and commits are searched, including historical versions of files.

Paste sites

Text dumps are checked for your domains, internal hostnames, secrets, and staff accounts.

App stores and APK sites

Official stores and third-party download sites are checked for apps using your name or logo.

Social media

Accounts, posts, and replies are checked for people posing as your organization, support team, or staff.

Search results and ads

Search listings and paid ads are checked for copied brands, fake downloads, support numbers, and sign-in pages.

Dark web forums and markets

Listings and discussions mentioning your organization, stolen data, or access to your systems are collected.

Telegram

Channels and bots are monitored for your brand, customer accounts, and fraud tooling targeting your services.

Ransomware leak sites

Posts naming your organization or domains are checked for claims of stolen data.

Stealer logs

Records collected by infostealer malware are matched to your domains and staff accounts.

The same scoring and case handling apply across sources. A suspicious domain, exposed key, and fake support account can be assessed without creating separate processes for each type of finding.

Look-Alike Domains and Clones

Look-alike domain monitoring finds registrations and web pages that imitate your brand, including copies of your real sign-in, payment, or customer portal pages. The Brand monitor examines both the domain name and what the site actually serves, because registration alone does not establish malicious use.

ThreatDefenceFAIR 64Search this page…secops › acmeacme-corp24h
Domain Impersonation
6Fresh (90d)
214Derived
41Parked
238Lookalikes
3Brands Targeted
Top lookalike domainsscored live, armed or parked
DomainSignalsState
acmec0rp.comCloned login page, fresh certificateLive
acme-corp-support.comMail records, no websiteArmed
acmecorp-payroll.netRegistered 3 days agoNew
acnecorp.comParked pageParked
acmecorp.com.coFor saleParked
Findings by sourcelast 30 days
SourceFindings
Look-alike domains238
Social media4
Mobile apps1
Code and paste sites2
Search and ads1
Event View3 need action
EventLookalikeBrandRegistrarNext
Cloned login page liveacmec0rp.comacmecorp.comExample Registrar LLCBlocked, takedown queued
Fake support account@acme_support_helpacmecorp.comSocial platformReport drafted
Mail records addedacme-corp-support.comacmecorp.comExample Registrar LLCBlocked in email
Typosquats

Misspellings, character swaps, and alternate top-level domains are generated and checked against your registered names.

Homoglyphs

Similar-looking characters and combinations are checked, including “rn” in place of “m” in acrnecorp.com.

Combo words

Domains adding terms such as “support” or “login” to your brand are identified for review.

Mail and live page checks

The agent checks mail records and active web content. A domain with mail configured or a live form deserves closer attention than an unused registration.

Cloned sites

Fake login, portal, and payment pages are compared with genuine pages using logos, favicons, and HTML.

Captured evidence

Cloned pages are screenshotted, and the phishing kit is captured where available.

A domain can remain parked before it begins serving a page or accepting mail. The agent keeps it under watch and updates its priority as the observed activity changes.

Read about typosquatting >

Code and Secrets in Public

The Brand monitor searches public code repositories and paste sites for credentials, internal configuration, personal data, and malicious code associated with your organization. An employee, contractor, or supplier can expose material through an account your security team does not control, including material later removed from the current version of a file.

ThreatDefenceFAIR 64Search this page…secops › acmeacme-corp24h
Code Exposure
Code and paste findingspublic repositories, gists, commit history, paste sites
SeverityRepository or pasteFileWhat leakedStateSeen
CRITICALvendor-dev/acme-portal-apiconfig/prod.ymlDatabase password, 3 API keysValidtoday
HIGHjsmith/acme-toolscustomers.xlsx (deleted, in history)Customer recordsData2d ago
HIGHgist: a91f…deploy.shCloud access keyRevoked4d ago
MEDIUMkitdev/phish-templatesacme/login.htmlPhishing kit using the brandKit6d ago
LOWpaste sitepaste 7Hc2…Internal hostnames listedInfo9d ago
vendor-dev/acme-portal-apipublic repository
Fileconfig/prod.yml, commit 4e1c9a2OwnerVendor developer accountSecretsDatabase password, 3 API keysKey checkLive on db.acmecorp.comFirst pushedToday 08:02
Done: owner told to rotate the keys first. Sign-in and database logs searched for the keys since 08:02, no use found. Removal request sent to the repository host and the vendor.
Keys and tokens

Exposed API keys, cloud credentials, and passwords are linked to the services they can access.

Signing secrets

Keys used to sign application sessions receive high priority because possession can allow fraudulent sessions.

Hosts and configuration

Scripts, configuration files, internal hostnames, and connection strings are flagged for review.

Records in repositories

Public customer or staff exports and spreadsheets are treated as potential data exposure.

Commit history

The agent reads earlier commits, including secrets deleted from the latest version but still available in repository history.

Vendor and personal accounts

Public repositories held by suppliers, contractors, and staff are matched against your names and hostnames.

Gists and pastes

Shared configuration blocks and troubleshooting extracts are checked for sensitive information.

Repositories aimed at you

Phishing kits using your sign-in page and fake applications published in code repositories are passed to the Takedown agent.

Secret scanning and push protection within your own repositories remain useful. External brand monitoring extends the search to public code you do not administer.

Rotation and Log Checks

Leaked secrets need to be invalidated before their public copies are removed. A deleted file or private repository does not invalidate a key already copied elsewhere, so the system owner rotates or revokes it first. For environments ThreatDefence monitors, the SOC searches available logs for activity throughout the exposure period.

Leak typeThe owner’s first stepWhat the SOC searches
Cloud access keyDisable the key and issue a replacementCloud audit logs for calls signed with the old key
SaaS API key or tokenRevoke it in the service and swap in a new oneThe service’s audit trail and any connected accounts
Database or server passwordSet a new password and update the applications that use itSign-ins to that database or server since the leak
Token-signing secretReplace the secret, which ends every session signed with itApplication logs for odd sessions and admin actions
User passwordReset the password, then revoke the account’s active sessionsSign-in history from new locations, devices and networks
Customer or staff recordsTake the data down and record what was exposedThe system the records came from and the people affected
Repository historyRewrite or remove the history once the secret is deadThe hostnames and system details old commits still reveal

Evidence of secret use becomes a SOC investigation, with the service’s 3 minute average response time. When the available logs show no signs of use, the finding is closed with a record of the checks performed and the period reviewed.

Read about secrets in public code repositories >

Fake Apps, Accounts and Ads

The Brand monitor looks for fake apps, social accounts, search results, and advertisements that misuse your identity to reach customers. These copies may try to collect credentials, one-time codes, payment information, or downloads under the appearance of an official service.

Repackaged apps

Rebuilt versions of your app with added code are sought in official app stores and third-party APK sites.

Unofficial apps

Apps using your name or logo without your authorization are recorded with their publisher and download source.

Fake company and support accounts

Impersonating social profiles are identified, including accounts replying directly to your customers.

Scam posts and ads

Fraudulent offers and download advertisements using your brand are captured with their destinations.

Search abuse

Brand-related ads, bogus help or download pages, and fake phone numbers in search results are flagged.

The agent retains the account, app, listing, or destination as evidence, so an analyst can distinguish an impersonation attempt from legitimate third-party activity before action is taken.

Read about fake apps >

Executive and Staff Impersonation

Executive impersonation monitoring finds public profiles and messages that present an attacker as someone from your organization. The Brand monitor checks the people you specify, with attention to fraud and attempts to obtain personal information or access.

Fake profiles

Social profiles copying an executive’s or employee’s name, photograph, or job title are identified.

Fake recruiters and job offers

Recruitment accounts and job advertisements misusing your organization are flagged when they seek personal details or payments.

Supplier payment lures

Messages claiming to represent your staff and requesting changes to supplier payment details are recorded for blocking and takedown.

You decide which executives and staff are monitored and can update the list when responsibilities change. A matching name alone is not enough to establish impersonation, so uncertain cases go to a SOC analyst.

Dark Web and Telegram

Dark web monitoring searches criminal forums, markets, Telegram channels, ransomware leak sites, and stealer logs for credentials, data, and access associated with your organization. The Brand monitor matches findings against your domains, staff identities, and customer accounts, then presents them in the Dark Web Assessment view for your team and the SOC. Records are held in your hosting region of Australia or the United States.

ThreatDefenceFAIR 64Search this page…secops › acmeacme-corp24h
Dark Web Assessment
Credential exposures, findings, intel alerts, ransomware leaks and threat actors for acme-corp
Credential Exposures9FindingsIntel AlertsEASM DomainsMonitored AssetsRansomware PostsThreat Actors
Domain: acmecorp.comSeverity: AnyStatus: AnySource: AllSearch
SeverityIdentityTypeWhat was foundTargetStatusDiscovered
CRITICALj.lee@acmecorp.comStealer logSession cookies, saved passwordsvpn.acmecorp.comValid, reset and sessions revoked2h ago
HIGHfinance@acmecorp.comStealer logSaved passwordsportal.acmecorp.comChecking sign-in logs5h ago
HIGHr.patel@acmecorp.comCombo listEmail and passwordlogin.microsoftonline.comNo longer valid1d ago
MEDIUMacmecorp.comAccess for saleVPN access offered on a forumvpn.acmecorp.comAnalyst reviewing1d ago
MEDIUMacmecorp.comTelegramMention in a fraud channelacmecorp.comWatching3d ago
LOWm.chen@acmecorp.comBreach recordOld third-party breachthird-party siteClosed, not reused6d ago
j.lee@acmecorp.com: session cookies for the VPN in a stealer log from 12 Nov. The password was still valid. Password reset and sessions revoked at 09:14; no sign-ins from the stealer’s address in 30 days of logs.
ExposureWhat it isWhat follows
Leaked loginsStaff and customer usernames and passwords from breaches and combo listsClosed through the credential steps in the next section
Stealer log recordsThe haul from one infected device: saved logins, session cookies, the device name and user, the malware family and the dateHandled first, since a session cookie can be replayed without the password or the second factor
Access for saleListings offering VPN, remote access, email or cloud accounts said to belong to youAn analyst compares the claim with your environment, and the agents hunt for the route it describes
Data for saleDatabases, exports and document sets a seller says came from your systemsCaptured with the advertising post and raised for analyst review
Ransomware leak site postsEntries naming your organization and what the group claims to holdConfirmed by an analyst, and for monitored environments the SOC opens an incident and searches for the intrusion
Telegram fraud toolingChannels and bots that sell accounts on your service or ask customers for one-time codesRecorded with the channel and watched for new posts
MentionsForum threads and channel posts that name your organization, domains or executives as a targetRaised for analyst review and followed for new activity

An offer of access or stolen data is a claim until it can be assessed. Previously handled breach records are linked to their existing findings when they reappear, so repeated listings add context without becoming duplicate alerts.

Closing a Leaked Credential

A leaked credential needs an account check, an assessment of past use, and an appropriate reset or revocation. For environments ThreatDefence monitors, the SOC follows credential findings through closure under your procedures. Stealer log details can also identify whether the infected device belongs to your managed environment.

1
MatchThe agent links the exposed username to an identity in your directory and checks whether the account remains enabled.
2
TestWhere connected services permit, the SOC checks whether the leaked password still works.
3
SearchAnalysts examine sign-in records from the leak date for unusual locations, devices, and networks.
4
Reset, then revokeThe password is changed before active sessions are revoked, preventing reuse of the password and ending stolen sessions.
5
InvestigateEvidence of use opens an investigation, with agents tracing what the account or session accessed in the monitored environment.

You receive a record of the exposure, the account involved, the checks completed, and the actions taken. For stealer logs, the infected machine’s details help determine the remaining response.

Read about stealer logs >

How Findings Are Scored

The Brand monitor scores findings according to the observed risk, so a live credential-harvesting page is handled ahead of an unused look-alike domain. The score accounts for what the asset does, whom it targets, and the available hosting and registration context.

FactorWhat the agent checksWhat raises the score
Live or parkedWhether a page, form or mail record is activeA live page or a working mail setup
What it collectsPasswords, payment details, one-time codes or personal dataA form that asks for credentials or payment
Who it targetsCustomers, staff, suppliers or executivesTargeting of people with access or authority
Age and hostingRegistration date, hosting provider and neighboring sitesA fresh registration on hosting known for abuse

Scoring determines investigation priority, not proof of malicious intent. The agent continues watching parked domains, and an active page or mail configuration can raise a case’s priority when its behavior changes.

See the Brand Monitor at Work

Watch the Brand monitor find a look-alike domain, a leaked key and a stolen login, and follow each one to blocking, rotation or takedown in a live demo.

What the demo shows
  • A scored look-alike domain with its evidence
  • A leaked key in public code and its rotation
  • A stealer log login checked against sign-in logs
  • A takedown from approval to offline

From Finding to Response

Once scored, a finding passes to the agent that can act on it. An analyst stays involved wherever a decision has consequences.

1
DiscoverThe Brand monitor records the source, supporting evidence, and score for each finding.
2
ProveThe agent captures the relevant page, kit, account, or other material so its suspected misuse can be reviewed.
3
BlockAI Defender blocks traffic to confirmed domains and addresses within your policy, while the Infrastructure hunter maps related domains and servers.
4
Take downThe Takedown agent prepares a removal case and, after your approval, submits requests to the relevant host, registrar, or platform.
5
EscalateFraud and other crime are referred to the authorities where required, while each removal request remains tracked until the content is gone.

The case connects the original evidence, protective action, approvals, and removal status. Blocking within the protected environment and removing content from the internet are separate steps.

Hunting Attacker Infrastructure

The Infrastructure hunter follows a confirmed domain, server, or suspicious link to find related attacker infrastructure. A starting indicator such as acmec0rp.com can lead to sibling domains, reused servers, and matching phishing kits. Shared infrastructure can also belong to unrelated sites, so the agent records and weighs the evidence for each connection.

ThreatDefenceFAIR 64Search this page…secops › acmeacme-corp24h
Infrastructure Hunter
Pivot mapregistration, passive DNS, certificates, hosting, fingerprints
name servercertificatekit fingerprintsame server15 namessame kitacmec0rp.comseed from Brand monitorns1.dns-park.examplename serverone certificate15 namesfavicon 9c1e44b0phishing kit14 sibling domainsnot yet used2 IP addressessame hosting
Outcomebefore the next wave
ResultDetail
BlockedDomains and IPs pushed to email, endpoint and firewall blocks
SharedIOCs sent to the threat hunter and every protected environment
QueuedEvidence pack per domain sent to the takedown agent
Registration details

Registrar, registration dates, name servers, and WHOIS records help associate domains that may have been registered together.

DNS history

Passive DNS identifies domains that previously resolved to shared servers, including names targeting other brands.

Certificate logs

Public certificate records can expose related hostnames before their websites become active.

Hosting and fingerprints

ASN, neighboring sites, bulletproof hosting, favicon hashes, HTML, kit files, and JARM and JA4 fingerprints help connect reused infrastructure.

Live checks

Hosts are checked for their current content and identified as live, parked, or preparing to launch.

Blocked before launch

Under your policy, AI Defender can block confirmed domains and addresses through email, endpoint, and firewall controls, sometimes before the first phishing email is sent.

Indicators shared

Confirmed indicators are distributed to every environment ThreatDefence protects, and the SOC checks for earlier contact with the identified infrastructure.

Confirmed domains and servers also receive evidence packs for the Takedown agent. The same investigation therefore supports preventive blocks, historical checks, and removal requests.

Takedowns Tracked Until Offline

The Takedown agent prepares and follows evidence-backed requests to remove confirmed impersonation and exposed content. Nothing is submitted until the approver named in your policy signs off. Your team, staff, and customers are also informed which pages, apps, and accounts are genuine while a fake remains active.

ThreatDefenceFAIR 64Search this page…secops › acmeacme-corp24h
Takedowns
1Waiting for approval
2Reported
2Offline or removed
5Evidence packs
3Watching for return
Takedown requestsnothing is sent before your approval
TargetTypeSent toEvidenceApprovalState
acmec0rp.comCloned login pageRegistrar and hostscreenshots, kit, WHOIS, DNSApproved 07:55Offline, watching
@acme_support_helpFake support accountSocial platformprofile captures, postsApprovedReported
Acme Rewards (APK)Repackaged appAPK site, app storepackage hash, signing certApprovedReported
acmecorp-payroll.netPhishing pageRegistrar, blocklistsscreenshots, certificateWaiting for youDrafted
vendor-dev/acme-portal-apiLeaked codeRepository hostcommit, file, ownerApprovedRemoved
Evidence pack

Screenshots, WHOIS, DNS and hosting records, kit files, certificates, fingerprints, and a timeline establish what the target copies and where it operates.

Your approval

The named approver reviews the finding, score, supporting evidence, and recipient before approving, holding, or closing the request with a reason.

Registrars and hosts

Registrars are asked to suspend look-alike domains, while hosts receive requests to remove cloned pages, phishing kits, and fake downloads.

Stores, platforms and code hosts

App stores, social networks, and repository services receive requests involving fake apps, impersonation accounts, or leaked and malicious code.

Browser blocklists

Reports to browser blocklists help warn visitors outside your protected environment while removal is pending.

Authorities

Fraud and other criminal activity can be referred to the national cyber agency, police, or regulator where appropriate.

Follow-up until offline

The agent rechecks each target and follows up on outstanding requests, closing them when the content is removed.

Copies that return

If the same clone appears at another domain or host, it becomes a new case with its own evidence and approval.

The removal decision ultimately sits with the registrar, host, or platform receiving the request. ThreatDefence keeps the case open and verifies the outcome rather than treating submission as a successful takedown.

Analysts in the Loop

ThreatDefence’s 24x7 SOC analysts review significant findings and control decisions that require human judgment. The agents continue searching and collecting evidence, while analysts provide the confirmation and coordination your team needs.

Policy

Analysts work with your team on the rules agents follow, including actions requiring your sign-off.

Confirmation

Significant findings are reviewed with their evidence before they are escalated to your team.

Approval

Analysts authorize containment and takedown activity within your policy once the required customer approval has been given.

Uncertain cases

A suspected partner domain, legitimate reseller app, or genuine staff profile is checked by an analyst before it is treated as misuse.

A review can confirm misuse, request more context, or close a legitimate finding with its reason recorded. Your team works from the same case evidence rather than an unexplained alert.

Brand Monitoring for Clients

MSPs and MSSPs can provide brand monitoring to their customers under their own brand, using the ThreatDefence platform and SOC. Each client has a separate set of identifiers and actions to manage.

Per-client watch lists

Partners choose the domains, brands, apps, code accounts, and executives or staff covered for each client.

Shared handling

Partners work with ThreatDefence’s SOC on confirmed findings, takedown approvals, secret rotation, and credential resets.

Outside-in first

Monitoring can start from a client’s brand and domain names without an integration into its systems.

Connecting identity and sign-in data later adds the ability to assess leaked credentials against the client’s environment. The partner remains involved in the approvals and response decisions appropriate to that client.

Start Brand Monitoring

Brand monitoring begins with the names, domains, applications, and people your organization wants to protect. The initial external sweep requires no installation or connection to internal systems.

1
Name what to watchProvide your domains, important hostnames, brand and product names, official apps, GitHub or GitLab organizations, and executives to monitor.
2
Review the first sweepThe Brand monitor checks its sources for existing impersonation and leaks, including historical commits and previously collected credentials. A SOC analyst reviews the findings with your team.
3
Connect identityConnecting your identity provider and sign-in logs allows the SOC to check exposed passwords and investigate whether accounts have been used.
4
Agree the responseConfirm who approves takedowns and password resets, and who rotates each type of secret. The agents then handle new findings under those rules.

Talk to Our Experts

See how ThreatDefence automates security monitoring, compliance and cyber risk management in one platform.

    I'm an MSP, MSSP, or reseller

    By submitting this form, you accept the terms in our privacy policy.

    Frequently Asked Questions

    What is brand monitoring?

    Brand monitoring is the ongoing search for misuse of your organization’s name, domains, identities, and data outside systems you directly control. ThreatDefence covers look-alike domains, fake sites, apps and social profiles, exposed code, and stolen credentials. Its Brand monitor agent discovers and scores findings, while a 24x7 SOC validates significant cases and coordinates approved protective action and takedowns. The focus is actionable misuse, rather than mentions of your brand alone.

    How is brand monitoring different from attack surface management?

    Brand monitoring identifies impersonation and leaked material associated with your organization, including domains or accounts that an attacker created and public code that you do not own. Attack surface management examines the systems, services, and assets your organization exposes. A leaked configuration file can be relevant to both: brand monitoring finds the public disclosure, while attack surface management can examine a named hostname. Both views help establish context, but they answer different questions.

    Does brand monitoring include dark web monitoring?

    Yes. ThreatDefence monitors dark web forums and markets, Telegram channels, ransomware leak sites, and stealer logs for your organization, people, and customer accounts. A listing can be a repeated breach record, an unverified claim of access, or an exposed credential requiring action. The SOC reviews the evidence, links repeat records to existing cases, and, for monitored environments, checks leaked staff credentials against available identity and sign-in records before coordinating closure.

    Do you find API keys leaked in public code?

    Yes. The Brand monitor searches public GitHub and GitLab repositories, gists, pastes, and earlier commits, including material posted by contractors or suppliers. Finding a secret does not show whether it has been used. The owner first disables or rotates the affected credential, and ThreatDefence’s SOC checks available logs for activity during the exposure period. The finding records the response and any evidence of misuse, even when the public file has already been removed.

    What happens when a finding turns out to be legitimate?

    An analyst reviews the evidence and closes a legitimate finding with the reason recorded. Similar domain names may belong to partners, and an unfamiliar app or social profile may be authorized. ThreatDefence checks these cases rather than assuming every match is hostile, involving your team when ownership is unclear. The source remains part of the assessment, but a confirmed legitimate case does not trigger a takedown request or an unnecessary misuse alert.

    Can you watch for impersonation of our executives?

    Yes. You choose which executives and employees the Brand monitor should watch, and the list can change as their roles change. The agent searches for copied names, photographs, and titles, as well as fake recruitment offers and messages claiming to request supplier payment changes. SOC analysts review significant matches to determine whether an account or message is impersonation. Confirmed cases can then be prepared for blocking or takedown under your policy.

    Is anything taken down without our approval?

    No. The Takedown agent prepares the case and supporting evidence, but waits for your named approver before submitting a removal request. Approved cases are sent to the relevant registrar, host, app store, social platform, code host, or blocklist, as appropriate. The receiving party controls removal, so a request does not itself mean the content is offline. The agent follows open requests and verifies that the content has gone before closing them.

    Do we need to install or connect anything?

    No. The first external sweep uses the domains, brand names, official apps, code organizations, and people you provide, without software installation or internal integrations. Connecting an identity provider and sign-in logs is a later step for organizations that want the SOC to check exposed passwords, investigate account use, and coordinate resets. The external monitoring can therefore start before those connections are available, while credential investigation depth depends on the data the SOC can access.