CYBER ATTACK / OTHER

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.

THE STORY

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 TO DO

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:

01 / WHAT WE KNOW

Lakeel data breach: the details

Reports on the Lakeel data breach each day4 Nov to 17 Nov · today is lighter, still counting
See the numbers
DayReports
4 Nov0
5 Nov0
6 Nov0
7 Nov0
8 Nov0
9 Nov0
10 Nov0
11 Nov0
12 Nov0
13 Nov0
14 Nov0
15 Nov0
16 Nov2
17 Nov (so far)1

More cyber attacks in Japan

02 / LATEST

Latest Lakeel news

TIMELINE

Lakeel data breach: timeline

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.