Ransomware Tracker by ExposureDrift
Dashboard / Victims / EWM Group

EWM Group was listed on 28 October 2026 by the aurora ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). aurora listed 17 organizations that month and 58 in total.

  • Listed 21 days ago.
  • 1147 organizations were listed by all groups in October 2026, see the month.
  • 62 in Financial Services that month.
  • 36 in GB that month.

Updated 2026-11-18 11:12 UTC. Data: public leak-site listings. How we work.

EWM Group corporate emblem
Listed by aurora Disclosed: 2026-10-28 13:00 UTC

EWM Group

Financial Services GB

Threat Group Post & Evidence

Listed by
Aurora 58 listings in total

The listing states no data size and no ransom demand.

No capture of the original post

We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.

The group's leak-site address is on paid plans

Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.

What the group says it holds

Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.

[fashion] EWM Group — the parent group behind Bonmarché, Edinburgh Woollen Mill, and Peacocks, three of the UK's best-known value fashion chains. The exposed material includes: 503,878 loyalty programme member records — full name, home address, date of birth, phone, mobile, email, loyalty card number, and transaction history spanning 2000–2026. ~21,000 employee records — salary, National Insurance number (via P11D), bank sort code and account number (WAGESTRANSFER database), home address, emergency contacts, maternity/paternity data, sickness absence, accident reports with injury details. <redacted> <redacted> <redacted> <redacted> <redacted> 100+ GB of Outlook PST email archives — complete email histories for named staff members spanning years of business operations. 313+ SQL Server database backups across 122 unique databases — the entire digital brain of the retail operation. 83 GB of…
Show the full post (985 characters)

[fashion] EWM Group — the parent group behind Bonmarché, Edinburgh Woollen Mill, and Peacocks, three of the UK's best-known value fashion chains. The exposed material includes: 503,878 loyalty programme member records — full name, home address, date of birth, phone, mobile, email, loyalty card number, and transaction history spanning 2000–2026. ~21,000 employee records — salary, National Insurance number (via P11D), bank sort code and account number (WAGESTRANSFER database), home address, emergency contacts, maternity/paternity data, sickness absence, accident reports with injury details. <redacted> <redacted> <redacted> <redacted> <redacted> 100+ GB of Outlook PST email archives — complete email histories for named staff members spanning years of business operations. 313+ SQL Server database backups across 122 unique databases — the entire digital brain of the retail operation. 83 GB of e-commerce transaction data — every online order from January 2021 to August 2026.

Amounts as written

  • 21,000 employee
  • 100+ GB
  • 83 GB

Kinds of data mentioned

  • Payroll and salaries

    “…and transaction history spanning 2000–2026. ~21,000 employee records — salary, National Insurance number (via P11D), bank sort code and account number (WAGESTRANSFER database),…”

  • Email and communications

    “…member records — full name, home address, date of birth, phone, mobile, email, loyalty card number, and transaction history spanning 2000–2026. ~21,000 employee records…”

  • Customer or client data

    “The exposed material includes: 503,878 loyalty programme member records — full name, home address, date of birth, phone, mobile, email, loyalty card number,…”

  • Employee and HR records

    “…loyalty card number, and transaction history spanning 2000–2026. ~21,000 employee records — salary, National Insurance number (via P11D), bank sort code and account number…”

  • Databases and backups

    “…Insurance number (via P11D), bank sort code and account number (WAGESTRANSFER database), home address, emergency contacts, maternity/paternity data, sickness absence, accident reports…”

What to do about this listing

Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.

If you work with EWM Group (customer, supplier or partner)

Within 3 days

  • Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
  • Ask EWM Group directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
  • Review what EWM Group can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
  • Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, email and communications, employee and hr records.
  • Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: payroll and salaries.
  • Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.

Within 30 days

  • Keep watching EWM Group A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are EWM Group

First 24 hours

  • Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: email and communications, customer or client data, payroll and salaries.
  • Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: payroll and salaries.

Within 3 days

  • Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
  • Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
  • Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
  • Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 21,000 employee, 100+ GB, 83 GB. Treat group figures as unverified.
  • Check regulatory and stakeholder notification duties United Kingdom: UK GDPR requires notifying the ICO within 72 hours of becoming aware of a reportable personal data breach. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United Kingdom.

Within 30 days

  • Check shared suppliers and software List the suppliers and software you share with other Financial Services organizations and ask them whether they were affected. Why: aurora listed 2 other Financial Services organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
  • Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
  • Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
  • Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.

Listing details

Resolved Domain Not stated
Industry Vertical Financial Services
Country GB
Enrichment Status ENRICHED

Listing severity score (heuristic)

48/100 • GUARDED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 10/30 pts
Commercial and general business
2. Group tier 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 18/25 pts
Larger claim: gigabytes, or business or financial records named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence

No scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.

Launch Attack Surface Recon →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Not Disclosed / Unresolved
DNS Authority Standard Authoritative
Edge CDN / Shield None
SPF Record Missing
DMARC Policy Missing
Public DNS records only • no port scanning

More Claims by aurora

All →
Sice Previt S.p.A.
Manufacturing 2026-11-17 09:09 UTC
Johnson Development Corp.
Financial Services 2026-11-09 12:44 UTC
Rapid Manufacturing
Manufacturing 2026-10-30 15:03 UTC
CP Manufacturing, Inc.
Manufacturing 2026-10-30 13:08 UTC
Meleghy Automotive & Cie. GmbH
Manufacturing 2026-10-28 10:05 UTC
GreenbergFarrow
Professional Services 2026-10-27 12:11 UTC