ShinyHunters 'pay or leak' extortion leaks Questel data; 1.2M email addresses added to Have I Been Pwned
In August 2026, French intellectual property software and services company Questel was targeted in a ShinyHunters "pay or leak" extortion campaign. The group published a large corpus of data it claimed to have taken from the company. The data is largely corporate contact information tied to sales leads, support cases and marketing activities, and includes 1.2M unique email addresses. Have I Been Pwned added the dataset on 1 Sep 2026.
Technical Details
- Extortion model: "pay or leak" by ShinyHunters, followed by publication of the data.
- Exposed data: email addresses, names, employers, job titles, physical addresses and phone numbers.
- The data relates to sales leads, support cases and marketing activities.
- The breach occurred in August 2026. The article does not state the initial access method.
Remediation
- Use a password manager to generate and store strong, unique passwords, and change any password reused across accounts.
- Enable 2FA wherever it is supported.
- Affected contacts should be alert to targeted phishing that uses the leaked business details.
Linha do tempo
-
ShinyHunters 'pay or leak' extortion leaks Questel data; 1.2M email addresses added to Have I Been Pwned
ler a análise desta fonte ocultar
In August 2026, French intellectual property software and services company Questel was targeted in a ShinyHunters "pay or leak" extortion campaign. The group published a large corpus of data it claimed to have taken from the company. The data is largely corporate contact information tied to sales leads, support cases and marketing activities, and includes 1.2M unique email addresses. Have I Been Pwned added the dataset on 1 Sep 2026.
Technical Details
- Extortion model: "pay or leak" by ShinyHunters, followed by publication of the data.
- Exposed data: email addresses, names, employers, job titles, physical addresses and phone numbers.
- The data relates to sales leads, support cases and marketing activities.
- The breach occurred in August 2026. The article does not state the initial access method.
Remediation
- Use a password manager to generate and store strong, unique passwords, and change any password reused across accounts.
- Enable 2FA wherever it is supported.
- Affected contacts should be alert to targeted phishing that uses the leaked business details.