William Cook Holdings Limited was listed on 19 November 2026 by the aurora ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). aurora listed 6 organizations that month and 62 in total.
- Listed 1 day ago.
- 991 organizations were listed by all groups in November 2026, see the month.
- 144 in Manufacturing that month.
- 40 in GB that month.
Updated 2026-11-20 14:59 UTC. Data: public leak-site listings. How we work.
William Cook Holdings Limited
Threat Group Post & Evidence
- Listed by
- Aurora 62 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.
[defence] William Cook Holdings Limited, trading as William Cook Group, is a privately owned UK industrial group founded in 1840 and headquartered at Parkway Avenue, Sheffield S9 4UL, England (Reg. No. 3283010). The group operates through four principal divisions: Cook Defence Systems (armoured vehicle track systems and structural components), William Cook Rail (bogie and coupler systems for trains), William Cook Cast Products (specialist steel castings for nuclear, energy, naval, and architectural applications), and William Cook Intermodal (container securing devices). The group employs approximately 470 people across three plants in Sheffield, Leeds, and Stanhope (County Durham). Chairman Sir Andrew Cook CBE is the fifth-generation family owner. HEICO Corporation (NYSE: HEI) holds a majority stake in Cook Defence Systems through its Defence Electronics division. Key customers include B…
Show the full post (3259 characters)
[defence] William Cook Holdings Limited, trading as William Cook Group, is a privately owned UK industrial group founded in 1840 and headquartered at Parkway Avenue, Sheffield S9 4UL, England (Reg. No. 3283010). The group operates through four principal divisions: Cook Defence Systems (armoured vehicle track systems and structural components), William Cook Rail (bogie and coupler systems for trains), William Cook Cast Products (specialist steel castings for nuclear, energy, naval, and architectural applications), and William Cook Intermodal (container securing devices). The group employs approximately 470 people across three plants in Sheffield, Leeds, and Stanhope (County Durham). Chairman Sir Andrew Cook CBE is the fifth-generation family owner. HEICO Corporation (NYSE: HEI) holds a majority stake in Cook Defence Systems through its Defence Electronics division. Key customers include BAE Systems, Babcock, General Dynamics, Diehl Defence, Iveco Defence Vehicles, Rheinmetall, and multiple national ministries of defence. The dataset comprises 1.1 TB exfiltrated from the Stanhope site file server (WC-STAN-FILE01), capturing the company's entire digital operational footprint across 59 top-level directories and approximately 1,400,000 files: <redacted> <redacted> Employee personal data affecting an estimated 600-1,200 individuals: Powerhouse payroll database (967 MB, 6 backup sets with NI numbers, bank details, pay rates), 100+ named occupational health records (annual medicals, HAVS assessments, physio referrals, medical suspensions), 66+ employment liability claims, 3 employment tribunal cases, passport scan (Alex Kerr), 156 named employee folders, salary spreadsheets current to July 2024, P11D tax benefits-in-kind records, pension auto-enrolment data, and disciplinary records across 5 sites. Complete financial records: TASBooks accounting backups (31 files spanning 2016-2022 for William Cook Leeds Ltd and William Cook Rail Ltd), management accounts FY24-FY26, Royal Bank of Scotland transaction history through August 2026 (July 2026: £3.68M credits, £2.81M debits), BACS payment runs, credit card expenditure, budgets and forecasts, and the CDS Master financial workbook. The Enquiry V3 Access database (55 MB) contains the complete commercial enquiry management system with customer intelligence, order history, and contact logs. IT infrastructure reconnaissance data: 40 MB AccessEnum ACL dump of the entire file server share structure with Active Directory domain SIDs for both current (WILLIAMCOOK.LOCAL) and legacy (ASTRUM) domains, ESET endpoint security configuration with license key and PKCS#12 agent certificates, management server IPs for 3 sites, RDP configuration for Synchro ERP, VPN CA certificate (Astrum Main CA), and CWorks Plus CMMS maintenance management database with machine criticality ratings. Privileged legal material: 3 employment tribunal cases (Atkinson K, Davies K, Swatten R), 66+ employer liability insurance claims, redundancy records (6 subdirectories), NDAs and cooperation agreements with Ukraine, Excalibur Army, FFG, Global Ordnance, and BASF, and Sir Andrew Cook's personal files including passport applications, property documents (5 Thurloe Street), and pension correspondence.
Amounts as written
- 1.1 TB
- 1,400,000 files
- 967 MB
- 31 files
- 55 MB
- 40 MB
Kinds of data mentioned
-
Tax records
“…named employee folders, salary spreadsheets current to July 2024, P11D tax benefits-in-kind records, pension auto-enrolment data, and disciplinary records across 5 sites.…”
-
Accounting and ledgers
“…disciplinary records across 5 sites. Complete financial records: TASBooks accounting backups (31 files spanning 2016-2022 for William Cook Leeds Ltd and William Cook Rail Ltd),…”
-
Payroll and salaries
“…personal data affecting an estimated 600-1,200 individuals: Powerhouse payroll database (967 MB, 6 backup sets with NI numbers, bank details, pay rates), 100+ named occupational…”
-
Identity documents
“…suspensions), 66+ employment liability claims, 3 employment tribunal cases, passport scan (Alex Kerr), 156 named employee folders, salary spreadsheets current to July 2024, P11D…”
-
Medical or patient records
“…sets with NI numbers, bank details, pay rates), 100+ named occupational health records (annual medicals, HAVS assessments, physio referrals, medical suspensions), 66+ employment…”
-
Customer or client data
“…(55 MB) contains the complete commercial enquiry management system with customer intelligence, order history, and contact logs. IT infrastructure reconnaissance data: 40 MB…”
-
Employee and HR records
“…top-level directories and approximately 1,400,000 files: <redacted> <redacted> Employee personal data affecting an estimated 600-1,200 individuals: Powerhouse payroll database (967…”
-
Contracts and legal files
“…maintenance management database with machine criticality ratings. Privileged legal material: 3 employment tribunal cases (Atkinson K, Davies K, Swatten R), 66+ employer liability…”
-
Databases and backups
“…data affecting an estimated 600-1,200 individuals: Powerhouse payroll database (967 MB, 6 backup sets with NI numbers, bank details, pay rates), 100+ named occupational…”
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 William Cook Holdings Limited (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 William Cook Holdings Limited 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 William Cook Holdings Limited 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, identity documents, 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, accounting and ledgers, tax records.
- 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.
- If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.
Within 30 days
- Keep watching William Cook Holdings Limited 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 William Cook Holdings Limited
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: identity documents, 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, accounting and ledgers.
Within 3 days
- Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
- 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, identity documents.
- 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.
- 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: 1.1 TB, 1,400,000 files, 967 MB. 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. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United Kingdom.
Within 30 days
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
- Watch for tax-filing fraud Tell your tax advisers and, where available, tax authorities so fraudulent filings made with exposed identifiers can be caught early. Why: The post names: tax records.
- Check shared suppliers and software List the suppliers and software you share with other Manufacturing organizations and ask them whether they were affected. Why: aurora listed 10 other Manufacturing 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
Listing severity score (heuristic)
69/100 • ELEVATEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceNo 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 →Run a free passive scan on your own domain to see what an attacker can see from the outside.