MyRecon OSINT
Angel One
On 1 April 2023, Angel One was breached. 6,765,054 accounts were exposed, including bank account numbers, dates of birth, email addresses. MyRecon rates it 70/100, severe. That is about 25% of the population of Australia.
The story behind the breach
In July 2024, the Indian stock brokerage firm Angel One confirmed that data leaked online related to a breach that occurred in April 2023 . The leaked data included 7.9M user records containing 6.8M unique email addresses, along with names, physical addresses, phone numbers, bank account numbers, Permanent Account Numbers (PANs) and portfolio holdings. Angel One emphasised that the breach "has no impact on client securities, funds, or credentials".
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.
How did it happen?
The published account does not explain the exact way the data was obtained.
What was the motive?
The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.
Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.
What was the outcome?
6,765,054 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Bank account numbers, Dates of birth, Email addresses, Financial investments, Government issued IDs, Names, Phone numbers, Physical addresses.
What was exposed, and why it matters
- Bank account numbersEnables direct-debit fraud and gives a caller the detail needed to sound like the bank.
- Dates of birthOne of the three things call centres ask to verify identity, and it never changes.
- Email addressesThe address becomes a confirmed, active target, expect more phishing, better aimed.
- Financial investmentsAdds detail to a profile that can be assembled from several breaches at once.
- Government issued IDsPassport and licence numbers are used to prove identity to banks and telecoms, and they are effectively permanent.
- NamesTurns an anonymous address into an identified person, which is what makes targeted phishing possible.
- Phone numbersEnables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.
- Physical addressesWhere someone actually lives. Combined with a name this moves the risk off the internet.
What to do if you were in it
- Move two-factor authentication off SMS and onto an authenticator app, which a SIM swap cannot intercept.
- Check statements for the months after the breach date and ask your bank for a replacement card if the number was full.
- Consider a credit freeze. A government identifier cannot be changed, so limiting what can be opened in your name is the only real control.
- Be sceptical of post and callers who already know your address, knowing it is no longer evidence of anything.
- Expect better-aimed phishing. A message that already knows your name and where you have an account is the whole point of a breach like this.
Questions people ask about this breach
Was my email address in the Angel One breach?
Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.
What data was leaked in the Angel One breach?
bank account numbers, dates of birth, email addresses, financial investments, government issued ids, names, phone numbers, physical addresses. Each one is explained above, along with what it means for the person it belongs to.
When did it happen, and when did it become public?
The breach is dated 1 April 2023. It was published to Have I Been Pwned on 7 October 2026, a gap of 1285 days during which the data was already out.
Is the Angel One breach real?
Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.
How many people were affected?
6,765,054 accounts. That is about 25% of the population of Australia. That is accounts rather than people, one person often has several.
Read next
Also in the archive
Case Files: how the landmark breaches actually happened →
Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.