LAKEEL.
DATA BREACH
Lakeel (Japan) was hit by a data breach first reported on 16 November 2026. No group has been publicly named as behind it in these reports. 3 news reports in the last 14 days, 1 in the last 24 hours; the latest, from NOVAIST: “Lakeel leaks personal data of 140 people after unauthorised AWS access; follow-up report reveals access key theft”. See every attack on the live map.
What happened in the Lakeel data breach
Lakeel (株式会社ラキール), a Japanese company, disclosed unauthorised access to part of its Amazon Web Services (AWS) environment.
Lakeel said it found that an access key used in its AWS environment had been stolen. It traced the start of the incident to a shortfall in access control security settings on the server of its source code management system. In a different customer's environment, a third party had broken into a server and created unauthorised users.
Lakeel said traces of unauthorised access had also been found in some other customer environments, but no specific damage had been found so far and the checks were continuing. It said no personal data leak had been confirmed outside the one customer. Lakeel said it was carrying out detailed log checks of each customer environment with AWS's cooperation.
Nobody has been named as the attacker in the sources reviewed. Lakeel said it had dealt with the cause, and that the stolen access keys had been invalidated or updated. It said it had set up a headquarters team led by its president and had cut the network from outside as a safety measure. Lakeel said it was reporting the situation individually to customers who use its AWS environment.
- What was taken: Lakeel said personal names and email addresses of 140 employees and others were leaked from one customer's environment. In a second customer's environment, a third party gained access to a server and created unauthorised users. Lakeel said an AWS access key was stolen after attackers exploited a shortfall in access control settings on its source code management system server.
- Who is affected: Lakeel said 140 people's personal data was leaked from one customer's environment. It said traces of unauthorised access were found in some other customer environments, but no specific damage had been found yet and the investigation was continuing.
- Who is behind it: Nobody has been named as the attacker. Lakeel has not said who carried out the access.
- The response: It set up a countermeasures headquarters led by its president. It said the cause had been addressed and the stolen access keys had been invalidated or updated. It said it was carrying out log investigations with AWS's cooperation and reporting individually to customers who use its AWS environment.
Was my data taken in the Lakeel data breach?
For this data breach: If you are a customer of Lakeel who uses its AWS environment, watch for a individual report from the company about your environment.
Only Lakeel can confirm whose data was involved. If you are a customer, these five steps cover you either way:
- Look for an email or letter from Lakeel. Firms whose data is taken usually have to tell the people affected, and it says what was taken.
- If you have an account with Lakeel, change its password, and the password anywhere else you used the same one.
- Turn on two-step sign-in where you can, so a stolen password is not enough on its own.
- Expect scam emails, texts and calls that mention Lakeel or this breach. Do not click links in them; go to the real website yourself.
- Check whether your email address has turned up in known breaches at haveibeenpwned.com. In the UK, report money lost to fraud to Action Fraud.
Lakeel data breach: the details
- Type: Data breach
- Sector: Other
- Where: Japan
- Reports, last 14 days: 3
- Latest report: 04:04 UTC, 17 November 2026
See the numbers
| Day | Reports |
|---|---|
| 4 Nov | 0 |
| 5 Nov | 0 |
| 6 Nov | 0 |
| 7 Nov | 0 |
| 8 Nov | 0 |
| 9 Nov | 0 |
| 10 Nov | 0 |
| 11 Nov | 0 |
| 12 Nov | 0 |
| 13 Nov | 0 |
| 14 Nov | 0 |
| 15 Nov | 0 |
| 16 Nov | 2 |
| 17 Nov (so far) | 1 |
Latest Lakeel news
- Lakeel leaks personal data of 140 people after unauthorised AWS access; follow-up report reveals access key theftNOVAIST · Data breach · Japan · 17 Nov 2026, 04:04 UTC
- Lakeel AWS unauthorised access leads to leak of personal data of 140 people in customer environment and server intrusionYahoo!ニュース · Data breach · Japan · 16 Nov 2026, 01:55 UTC
- Unauthorized access to Lakeel's AWS environment leaks personal data of 140 people in customer environment and reveals server intrusionYahoo!ニュース · Data breach · Tokyo, Japan · 16 Nov 2026, 01:55 UTC
Lakeel data breach: timeline
- 2026-11-10: Lakeel detected an abnormal situation and confirmed unauthorised access from outside, cut network connections from outside and set up a countermeasures headquarters.
- 2026-11-11: Lakeel publicly announced the incident in its first report.
- 2026-11-12: Lakeel confirmed the leak of personal data of 140 people from one customer's environment.
- 2026-11-13: Lakeel published its second report, identifying the stolen AWS access key as the start of the incident and disclosing the server intrusion at a second customer.
Lakeel data breach: common questions
What happened to Lakeel?
Lakeel (Japan) was hit by a data breach first reported on 16 November 2026. No group has been publicly named as behind it in these reports.
What happened in the Lakeel data breach?
Lakeel said an AWS access key was stolen after attackers exploited a shortfall in access control settings on a source code management server. Names and email addresses of 140 people were leaked from one customer's environment, according to the company's second report.
How many people were affected by the Lakeel leak?
Lakeel said personal data of 140 employees and others was leaked from one customer's environment.
What data was leaked in the Lakeel incident?
Lakeel said the leaked data was limited to names and email addresses. The company's announcement did not report passwords as leaked.
Who is behind the Lakeel attack?
Nobody has been named as the attacker in the sources reviewed. Lakeel has not said who carried out the unauthorised access.
What is Lakeel doing in response?
Lakeel said it had invalidated or updated the stolen access keys and was running detailed log checks with AWS. It said it was reporting individually to customers who use its AWS environment.
Who is behind the Lakeel data breach?
No group has been publicly named in the reports collected here. Attribution can take weeks and is often disputed.
Was my data affected?
Only Lakeel can say whose data was involved; its own statement is usually linked from the latest reports below. If you are a customer, watch for emails or texts that mention the breach, change your password there and anywhere you reuse it, and turn on two-step sign-in.