All Breaches
December 12, 2020 Verified Sensitive Record Technology

Capital Economics Data Breach

The Capital Economics entry documents a third-party breach record dated 12 December 2020 and associated with capitaleconomics.com. Public sources report 263,829 records.

263.8 Thousand
Reported Records
6
Data Types
High
Severity
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

6
  • Email addresses
  • Employers
  • Job titles
  • Names
  • Phone numbers
  • Physical addresses

About This Breach

Verified data categories include email addresses, employers, job titles, names, phone numbers, and physical addresses.

Recorded data scope

  • Identity and contact data: Names, email addresses, phone numbers, and physical addresses.
  • Professional profile data: Employer names and job titles.

Potential impact

Contact details combined with professional profile data can support spear-phishing, executive or colleague impersonation, fraudulent invoice requests, and business-email-compromise attempts. Address and phone data may also be combined with other sources to build a more detailed identity profile. Passwords, bank-account details, and payment-card data are not listed in the recorded scope and should not be assumed to have been exposed.

Recommended actions

  1. Verify unusual payment, document, or credential requests claiming to come from Capital Economics, an employer, or a senior colleague through a second channel.
  2. Protect email accounts with unique passwords and two-factor authentication, and review active sessions and unexpected forwarding rules.
  3. When someone requests personal information by phone or email, call back through an official contact channel rather than using details in the message.
  4. Monitor unexpected mail, account-opening notices, or financial notifications and report suspicious activity to the relevant provider.

Scope note

Unverified person counts, data fields, and threat-actor claims are not treated as part of the public incident scope.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information