Skip to main content
Industry · Retail, e-commerce and consumer brands

Retail cybersecurity for the storefronts you never opened.

A retail brand is copied where its customers shop: look-alike storefronts, counterfeit listings, cloned apps and discount pages that take card details in its name. ShadowMap finds them at registration and on the platforms they trade on, and files the removals you authorise. It covers the estate behind the real storefront too: campaign sites, exposed payment keys and the platform suppliers a shop runs on.

“In sale season the fake storefronts go up faster than we can find them, and every one of them takes card details in our name.”

Takedowns are unlimited, subject to fair use, and filed through 86 provider relationships across 12 provider types. Registration and certificate feeds are checked daily for look-alike domains.

The frame

A retailer’s customers are attacked in places the retailer does not run

The controls a retailer owns protect the shop it built. The fraud its customers meet happens somewhere else.

A shopper searches for a brand, clicks a sponsored result and pays a storefront that carries the right logo, the right photography and a discount that looks like a seasonal sale. Nothing in that sequence touches the retailer’s infrastructure. No firewall log records it and no fraud model scores it, because the payment was never the retailer’s to see. It arrives later as a complaint, a dispute or a review that says the brand took the money and sent nothing. The same is true of a cloned shopping app in a third-party store, a counterfeit listing on a marketplace and a customer-care handle that asks for an order number and a card. All of it sits outside the perimeter, in a retailer’s name, and all of it is visible from outside. Finding it is a matter of matching what is published against what the brand really looks like: its marks, its imagery, its product copy and its real domains. Removing it is a matter of filing the right notice with whoever hosts it.

Where the exposure sits

Seven places a retail brand is exposed, front of house and back

The first three face the customer. The last four sit behind the real storefront. Each row names the capability that covers it.

WhereWhat is exposed thereCovered by
Look-alike storefronts Domains built from the brand name plus a sale, an outlet or a country, serving a copy of the real shop with a checkout that collects card details. Domain Monitoring
Registration and certificate feeds are checked daily, across generic and country-code top-level domains.
Apps, social shops and support handles Cloned shopping and loyalty apps in third-party stores, brand accounts selling through social platforms, and customer-care handles answering shoppers in the retailer’s name. Brand Protection
Matched on logos, imagery and product copy as well as on the name. An authorised reseller or franchisee is recorded as a known partner and stays suppressed.
The fake checkout itself The hosted page, the kit behind it and the infrastructure it is served from. Website takedown
The removal is filed on your authorisation with the host, registrar or platform that can act on it.
Campaign and seasonal sites Sale microsites, agency-built landing pages and staging copies of the shop, launched for a season and left answering after it. Attack Surface Management
The external estate is rebuilt every 24 hours from the apex domain, so a site launched for a campaign is on the record while the campaign runs.
Payment keys and shop code Payment-gateway keys, storefront-platform tokens and database connection strings pushed to public repositories by agencies and freelance developers under their own accounts. Data Exposure Monitoring
Where it is safe and authorised an exposed key is tested: is it live, and what does it open.
Customer accounts Shopper logins captured by infostealers and traded in logs that reference the retailer’s domain: the raw material of account takeover against stored cards, loyalty points and gift balances. Dark Web Monitoring
Customer credentials are reported to you for fraud and account-takeover prevention. They are not tested.
Platform and delivery suppliers The e-commerce platform, payment service providers, plug-in vendors and delivery partners that hold customer data or sit in the checkout path. Third-Party Risk Management
Suppliers are scored with the same categories and bands as your own estate. The standard licence includes 20 vendors.

Look-alike storefronts

What is exposed there
Domains built from the brand name plus a sale, an outlet or a country, serving a copy of the real shop with a checkout that collects card details.
Covered by
Domain Monitoring

Registration and certificate feeds are checked daily, across generic and country-code top-level domains.

Apps, social shops and support handles

What is exposed there
Cloned shopping and loyalty apps in third-party stores, brand accounts selling through social platforms, and customer-care handles answering shoppers in the retailer’s name.
Covered by
Brand Protection

Matched on logos, imagery and product copy as well as on the name. An authorised reseller or franchisee is recorded as a known partner and stays suppressed.

The fake checkout itself

What is exposed there
The hosted page, the kit behind it and the infrastructure it is served from.
Covered by
Website takedown

The removal is filed on your authorisation with the host, registrar or platform that can act on it.

Campaign and seasonal sites

What is exposed there
Sale microsites, agency-built landing pages and staging copies of the shop, launched for a season and left answering after it.

The external estate is rebuilt every 24 hours from the apex domain, so a site launched for a campaign is on the record while the campaign runs.

Payment keys and shop code

What is exposed there
Payment-gateway keys, storefront-platform tokens and database connection strings pushed to public repositories by agencies and freelance developers under their own accounts.

Where it is safe and authorised an exposed key is tested: is it live, and what does it open.

Customer accounts

What is exposed there
Shopper logins captured by infostealers and traded in logs that reference the retailer’s domain: the raw material of account takeover against stored cards, loyalty points and gift balances.

Customer credentials are reported to you for fraud and account-takeover prevention. They are not tested.

Platform and delivery suppliers

What is exposed there
The e-commerce platform, payment service providers, plug-in vendors and delivery partners that hold customer data or sit in the checkout path.

Suppliers are scored with the same categories and bands as your own estate. The standard licence includes 20 vendors.

A sale season

The work follows the calendar, and the order matters

A look-alike has to be registered before it can trade, and a campaign site has to launch before it can be forgotten. One peak season, in the order it happens.

What the sector answers to

Four texts a retailer taking cards and personal data works under

Each row cites the text or the body that publishes it. The right-hand column is the dated record ShadowMap holds beneath it.

TextWhat it saysWhat the monitoring record shows
PCI DSS The PCI Security Standards Council describes Approved Scanning Vendors as the firms that conduct external vulnerability scanning to validate adherence with the external scanning requirements of Requirement 11.3.2. It describes Requirements 6.4.3 and 11.6.1 as ensuring that payment page scripts are authorised, checked for integrity and monitored for tampering. What the internet-facing estate looked like between two scans, including storefronts and campaign sites outside the scan’s target list.
Sources: pcisecuritystandards.org, the Approved Scanning Vendors page and the Council’s note on its e-skimming guidance, read 18 November 2026. The ASV scan stays with your Approved Scanning Vendor.
GDPR, European Union Article 32(1) requires a controller and a processor to “implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk”. Article 33(1) requires a personal data breach to be notified to the supervisory authority “without undue delay and, where feasible, not later than 72 hours after having become aware of it”. When an exposure of customer data was first observed, where, and when it closed.
Source: Regulation (EU) 2016/679, EUR-Lex, read 18 November 2026.
NIS2 Directive, European Union Annex II lists digital providers among the other critical sectors, and names providers of online marketplaces first among them. Supplier and estate records for the risk-management measures Article 21 sets out.
Source: Directive (EU) 2022/2555, EUR-Lex, read 18 November 2026.
DPDP Act, India Section 8(5) of the Digital Personal Data Protection Act, 2023 requires a Data Fiduciary to protect personal data, including processing done on its behalf by a Data Processor, “by taking reasonable security safeguards to prevent personal data breach”. The observed external posture of each supplier processing customer data on the retailer’s behalf.
Source: the Act as published by MeitY, read 18 November 2026. Whether a text binds a given business is a determination for its compliance function. ShadowMap holds the dated monitoring record, never a compliance opinion.

PCI DSS

What it says
The PCI Security Standards Council describes Approved Scanning Vendors as the firms that conduct external vulnerability scanning to validate adherence with the external scanning requirements of Requirement 11.3.2. It describes Requirements 6.4.3 and 11.6.1 as ensuring that payment page scripts are authorised, checked for integrity and monitored for tampering.
What the monitoring record shows
What the internet-facing estate looked like between two scans, including storefronts and campaign sites outside the scan’s target list.

Sources: pcisecuritystandards.org, the Approved Scanning Vendors page and the Council’s note on its e-skimming guidance, read 18 November 2026. The ASV scan stays with your Approved Scanning Vendor.

GDPR, European Union

What it says
Article 32(1) requires a controller and a processor to “implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk”. Article 33(1) requires a personal data breach to be notified to the supervisory authority “without undue delay and, where feasible, not later than 72 hours after having become aware of it”.
What the monitoring record shows
When an exposure of customer data was first observed, where, and when it closed.

Source: Regulation (EU) 2016/679, EUR-Lex, read 18 November 2026.

NIS2 Directive, European Union

What it says
Annex II lists digital providers among the other critical sectors, and names providers of online marketplaces first among them.
What the monitoring record shows
Supplier and estate records for the risk-management measures Article 21 sets out.

Source: Directive (EU) 2022/2555, EUR-Lex, read 18 November 2026.

DPDP Act, India

What it says
Section 8(5) of the Digital Personal Data Protection Act, 2023 requires a Data Fiduciary to protect personal data, including processing done on its behalf by a Data Processor, “by taking reasonable security safeguards to prevent personal data breach”.
What the monitoring record shows
The observed external posture of each supplier processing customer data on the retailer’s behalf.

Source: the Act as published by MeitY, read 18 November 2026. Whether a text binds a given business is a determination for its compliance function. ShadowMap holds the dated monitoring record, never a compliance opinion.

Questions buyers ask

Before you evaluate this

The fake store is not on our infrastructure. Why is it ours to deal with?

Because the customer believes it is yours. The complaint, the dispute and the review arrive at the brand. The registrar and the host act on a notice, and a notice needs someone with standing to file it and the evidence to support it.

How many takedowns are included?

Takedowns are unlimited, subject to fair use. You raise each request from a confirmed finding and attest that you are authorised to act. The notice is then filed with the registrar, host, store or platform that can remove the listing, through 86 provider relationships across 12 provider types.

Our resellers and franchisees use our name legitimately. Will they be flagged?

Each match carries a disposition. An account on your authorised list is recorded as a known partner and stays suppressed, so the same reseller does not come back next month as a new finding. A match that cannot be settled from outside is held with its evidence and one question for you: is this yours?

Does this replace our PCI DSS external scan?

The external scan PCI DSS calls for stays with your Approved Scanning Vendor. ShadowMap runs every day between two of those scans and reaches what the scan was never pointed at: the campaign site an agency launched, the staging shop, and the storefronts that are not yours at all.

See who is selling under your name

Thirty minutes on one brand and one domain: the look-alikes registered against it, the listings and apps carrying its marks, and what your own campaigns left answering.