Skip to content
InYourGeek
visiteur@inyourgeek — shell
↹ compléter↑↓ historique⏎ ouvrirhelp
FR
← Back to the register

France Bourse

CriticalReportedMedia and leisure

On 10 October 2026, a threat actor announced the free release of a database of 16,425 customer records attributed to France Bourse, a French financial media outlet aimed at individual investors. According to samples reviewed by FrenchBreaches, the records reportedly contain names, postal addresses, phone numbers, email addresses, passwords readable in plain text, annual income ranges, professional details and subscription data. No banking data was seen in these samples. The full authenticity of the file and how it was obtained are unconfirmed, and the 16,425 rows do not necessarily match as many distinct individuals.

Combining contact details, income ranges and subscription data would let a malicious third party craft targeted fraudulent messages impersonating France Bourse or a financial adviser, and the readable passwords could be used to attempt access to other accounts.

Disclosed on
October 10, 2026
Incident dated
October 10, 2026
Sector
Media and leisure
Country
France
Cause
Undisclosed

Exposed data

  • Full name
  • Postal address
  • Phone number
  • Email address
  • Password (plaintext)
  • Employment data
  • Customer ID
  • Other personal data

You are only affected if you had an account or an order with this organisation.

What you can do

  • Change that password — and everywhere you reused it. That is how a leak spreads to your other accounts.
  • Turn on two-factor authentication on the affected accounts: a stolen password is then no longer enough.
  • Expect phishing attempts quoting your name and this company. A message that knows your details is not legitimate for that reason.
  • You can ask the organisation exactly what was exposed about you (right of access), and complain to the DPA if no answer comes within a month.

Sources

Entry built from the cited sources after a corroboration check, then reviewed before publication. Spotted an error, or have a correction? Write to us and the entry will be fixed. Contact