All Breaches
July 16, 2021 Verified Sensitive Record Firearms Sales Marketplace

Guntrader Data Breach

The 2021 Guntrader.uk breach reportedly used a vulnerability in an old iframe and occurred on July 16, 2021.

112 Thousand
Reported Records
11
Data Types
High
Severity
Oct 9, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

11
  • Email addresses
  • Names
  • Physical addresses
  • Geographic coordinates
  • Phone and fax numbers
  • IP addresses
  • Salutations
  • User-agent details
  • Hashed passwords
  • RFD issuing police-force context
  • Payment logs and advertised prices

About This Breach

The stolen SQL database covered records from 2016 through July 17; Guntrader notified users on July 21 and reported the event to the ICO. July 16 should remain the incident date and July 17 the data-coverage or snapshot endpoint.

The founder confirmed names and addresses were stolen but emphasized that records were not linked to particular firearms or proof of ownership. Direct inspection found coordinates, names, the issuing police force for RFD certificates, phones or faxes, bcrypt hashes, postcodes or addresses, and IPs, plus payment logs and advertised prices; it reported no card numbers, electronic gun registers, or police transfer-notification correspondence. These fields must not be assumed to co-occur for every person.

A public breach source reports 112,031 unique emails; this is not a count of people, firearm owners, licence holders, buyers, sellers, or households. The local job processed 111,290 email lines and produced 111,287 unique emails, 744 below a public breach source's measure. Other fields are not locally searchable.

A result cannot establish identity, an account, firearm or licence ownership, buyer, seller, or RFD status, household risk, a listing, price or payment, address or location, phone, IP, or password co-occurrence. Addresses, precise coordinates, police or RFD context, and firearm-market associations must not be publicly disclosed. An old password should be replaced where it was reused, and correct name or address details do not authenticate a sender.

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