> JapanHacked_
[Contained][Severity: Major][Credential abuse]

Eisai: an overseas employee account was misused and information on business partner contacts on the group cloud platform may have leaked

An overseas employee account was misused on April 28 and about 11,000 records of business partner contacts on the cloud platform may have leaked.

Disclosed

2023-05-19

Organizations involved

1

Leaked or at risk

Unknown

Downtime

Unknown

What happened

  1. In Japan time, an outsider using the account of an employee of an overseas group company accessed part of the information on the group cloud platform without authorization. It immediately blocked the access and strengthened network monitoring. [1] [2]

  2. It announced the case. It reported to the Personal Information Protection Commission and responded in line with each country's regulations. It set up a dedicated contact desk. [1] [2]

Impact

The people who may be affected are business partner contacts registered for work purposes from May 2018 to April 2023 in Microsoft products or the identity management system managed by the group (Teams project invitees, SharePoint access holders, Microsoft 365 group members and registrants of the identity system). About 11,000 records. Only names (where registered) and business email addresses may have leaked, and data on general consumers is not included. [1] [2]

Timeline

  1. Started, Detected 2023-04-28
  2. Disclosed 2023-05-19
  3. 21 days

Attack or cause

Method
[Credential abuse]
Impact
[Data leak]
Entry point
Stolen credentials

Data exposed or at risk

[Name][E-mail address]

Organizations involved

  • [Breached][Major]Tokyo, BunkyoManufacturing11,000 leaked

    Eisai Co., Ltd.

    The same announcement covers EA Pharma, Kan Research Institute and Sunplanet. The count is for the whole group including overseas affiliates.

Open in organization search

Sources

  1. [1][Official]不正アクセスによる個人情報流出の可能性に関するお詫びとご報告Eisai Co., Ltd. · 2023-05-19
  2. [2][News]エーザイグループのクラウドへ不正アクセス、約 11,000 件の取引先関係者情報が漏えいした可能性ScanNetSecurity · 2023-05-26 08:05