---
title: "Chargemap breach exposes emails and password hashes"
date: "2026-11-21"
author: "Ahsan Luqman"
canonical_url: "https://aliasfleet.com/blog/chargemap-data-breach"
tags: ["Data Breach", "Email Privacy", "Phishing"]
description: "Chargemap confirmed a breach on 8 November 2026 that exposed email addresses, usernames and password hashes. No victim count has been disclosed."
---

# Chargemap breach exposes emails and password hashes

Chargemap confirmed a breach on 8 November 2026 that exposed email addresses, usernames and password hashes. No victim count has been disclosed.

The Chargemap data breach is a November 2026 incident in which an attacker exploited a flaw in an old technical interface of the French electric vehicle charging platform and took email addresses, usernames and password hashes. Chargemap confirmed the breach on 18 November 2026, ten days after the attack on 8 November 2026. Banking data, payment methods, charging sessions and invoices were not affected, according to Chargemap. No victim count has been disclosed.

Chargemap maps charging stations across Europe and sells the Chargemap Pass, a charging badge for drivers. The platform has more than 3.5 million users in Europe, according to [Cybernews](https://cybernews.com/security/chargemap-ev-charging-app-data-breach/) and [HIFY Radar](http://hify.ai/radar/en/chargemap-confirms-breach-and-theft-of-user-data); that figure is the total user base, not a victim count. Chargemap disclosed the incident in a customer email and in a question-and-answer page on its help centre. The details in this article come from those two primary sources, with independent reporting from Cybernews, [SMTPedia](https://smtpedia.com/chargemap-breach-email-addresses-password-hashes/) and [The War Record](https://thewarrecord.com/events/ev-20261119-yyyx/).

## What happened and when

On 8 November 2026 an outside party exploited a security flaw in an old technical interface of Chargemap and extracted part of its user account data, according to [Chargemap's help-centre Q&A](https://help.chargemap.com/fr/articles/11583170). Chargemap states that its teams detected abnormal activity on 10 November 2026 and fixed the flaw on 12 November 2026. Chargemap notified the incident to the CNIL, the French data protection authority, on 13 November 2026, then analysed which data was concerned before informing users, so the notification would be reliable. Affected users received an email on 18 November 2026, sent from support@chargemap.com.

The customer email stated: "On 8 November 2026, Chargemap was the target of a cyberattack. An unauthorised person was able to access certain user account data, including yours." The full email was reproduced on the [Survive France forum](https://www.survivefrance.com/t/ev-charge-map-users/61553). Belgian broadcaster VRT NWS reported the story on 18 November 2026, the same day users were emailed, according to HIFY Radar and The War Record, which both cite the VRT report. Chargemap has started proceedings to file a criminal complaint and states that a full review of its applications is under way, with additional security measures being deployed.

## What the attacker obtained

For every affected account, the attacker obtained the email address, the username and the language of the app. Other fields were exposed only where the user had filled them in when signing up to Chargemap. That second group covers first and last name, phone number, date of birth, city and country, and the GPS coordinates of the city the user registered with. Chargemap states that the coordinates are those of the sign-up city, not the user's location and not their address. Profile pictures were exposed, along with a bio and website where the user had provided them, and the date of last login. Internal technical identifiers were also exposed.

For accounts created with a password, the attacker obtained a hash of the password, not the password itself. A hash is a one-way transformation, not the password in readable form, but a hash can be attacked. Cybernews notes that its research team warns the exposure of password hashes heightens the threat of account takeover, because tools exist to identify the hashing algorithm, crack the password by dictionary or brute-force attack, and then automate credential stuffing once it is cracked. For users who log in with Google, Facebook or Apple, the attacker obtained the identifier that lets that service recognise the Chargemap account. Chargemap states that this identifier alone does not allow anyone to log in as the user, on Chargemap or on Google, Facebook or Apple. For accounts with a subscription, the attacker obtained the subscription status, including whether the user subscribed to the Boost offer.

Users who have not logged in since April 2019 had their password stored in an older, weaker format. Chargemap asks those users to change it on Chargemap and on every service where they used the same one. The company does not name the old format. Some data from accounts deleted before the incident may also be affected. Chargemap states that it cannot contact those users individually, because the accounts are gone, and that the recommendations on its help-centre page apply to them as well, in particular if they used their Chargemap password on other services. About twenty users are in a separate category. Their Chargemap Pass badge numbers were affected, and Chargemap states that those users were informed specifically. For everyone else, the badge number was not affected.

## What the attacker did not obtain

No banking or financial data was affected, and payment methods, charging sessions including history, locations and amounts, invoices and postal addresses were all unaffected. Passwords in plain text were not exposed, and the information entered when ordering a Chargemap Pass badge, which sits in a different service, was not affected either. Chargemap lists the unaffected data first in its own Q&A, before the exposed list. The incident was a breach of account and profile data, not of payment data.

## Phishing danger

The exposed fields provide the material for targeted phishing messages. A message that includes a full name, a phone number, a date of birth, a city and a subscription status can present itself as coming from a company that knows the recipient. Chargemap warned affected users in its customer email: "Someone could use this data to send you fraudulent messages that seem credible." The combination of email address, name and Boost subscription status allows a fake renewal message or a fake badge message addressed to the recipient by name. The password hash adds a second risk. A hash that gets cracked becomes a working password on every service where the same password was reused. The mailbox carries the highest priority in that chain, because every password reset flows through it, and in this case the mailbox also receives Chargemap's own login verification codes.

## What a per-site alias changes

AliasFleet is an email alias service. A user creates one alias per website, and each alias forwards to the real inbox. When a site is breached, the address in the stolen file belongs to that site alone. The user pauses that alias and the leaked address stops working. In the Chargemap case, the address handed to Chargemap is the address now in the stolen file, and it is the address the phishing messages will target. A per-site alias would not have stopped the breach, and it would not have protected the name, phone number or date of birth, which Chargemap held regardless of the email address used. What it does is contain the email side: the phishing lands on an alias that names Chargemap as its source, and pausing the alias cuts off that channel without changing the real inbox address. The [guide to tracing which website leaked an email](https://aliasfleet.com/blog/which-website-leaked-my-email) explains how the arriving address names its source. The [guide on what to do when an email is in a data breach](https://aliasfleet.com/blog/what-to-do-when-your-email-is-in-a-data-breach) covers the password and phishing steps in order.

## Advice to affected users

Chargemap advised users who log in with a password to change it now, on Chargemap and on any other service where they use the same one, in particular their email, their bank or their social networks. Users who log in only with Google, Facebook or Apple do not need to change a Chargemap password, because no Chargemap password exists for those accounts. If they also have a Chargemap password, the change advice applies to them too. Chargemap advised users who reused that password on their mailbox to change the mailbox password first. A Chargemap account is protected by an extra email verification step on every sign-in, on the app and on the website. If a user reused the same password for Chargemap and for their mailbox, an attacker who recovers the password from its hash could reach the mailbox that receives the verification codes.

Chargemap also advised users to stay vigilant about emails, text messages or calls claiming to be from Chargemap and asking for personal information. Real Chargemap emails always come from an address ending in @chargemap.com. Chargemap advised users to check the sender address carefully. Chargemap will never ask for a password or bank details by email, text message or phone. Users were also told to check their charging history in the app regularly and to report any charging session they did not make.

Your address is probably in this file. [Check whether it is](https://www.aliasfleet.com/blog/how-to-check-if-your-email-was-leaked), do the password work above, and then fix the part you control: the address you hand out next time. One [AliasFleet](https://aliasfleet.com) alias per service means the next leak can only point back to the service that leaked it. [Founders Club is $7 a month, locked forever](https://aliasfleet.com/pricing), instead of $12. Early members only.

## What Chargemap has not said

Chargemap has not disclosed how many accounts were affected. The platform has more than 3.5 million users in Europe, but that is the total user base, not a victim count, and it must not be read as one. Some reporting has blurred this line: the Cybernews headline reads "3.5 million Europeans exposed", and its body says "over 3.5 million European users impacted". Chargemap itself has said nothing of the kind, and SMTPedia, HIFY Radar and The War Record all state explicitly that the company has not disclosed how many accounts were affected. Until Chargemap gives a number, there is no victim count.

No attacker group has claimed responsibility, no attribution has been reported by any outlet, and the exact intrusion method beyond a flaw in an old technical interface has not been described. Chargemap has said nothing about whether any of the stolen data has been misused, and no outlet reports confirmed misuse. No independent forensic report has been published, so the reassurances about payment data rest on Chargemap's own investigation so far. The CNIL was notified on 13 November 2026, and any regulatory outcome is still to come, so a follow-up is warranted if Chargemap discloses a victim count, if misuse is confirmed, or if the CNIL takes action.
