I’LL: CROSS POINT API-key abuse exposes one client’s member information
A client-specific API key was abused to obtain member data. The client and count are undisclosed; emergency safeguards include rotating all clients’ keys.
Disclosed
2026-11-10
Organizations involved
1
Leaked or at risk
Unknown
Downtime
Unknown
Abuse of a client-specific credential
Early on 7 November, I’LL confirmed that a legitimate API key assigned to one CROSS POINT client had escaped externally and was used to retrieve member information. It says this was not direct intrusion into the internal database, tampering, or exploitation of a program vulnerability. The client, affected count and key-exposure route are not disclosed. [1]
Potential fields include names, birth dates, gender, postal/contact details, member IDs/ranks, points, store-card and e-commerce account IDs, and purchase statistics. Card details and login passwords are not held. The affected key was revoked/reissued and source access blocked; safeguards including rotation of all clients’ keys were completed at 22:15 on 9 November. No evidence of exposure at other clients is confirmed. [1]
Timeline
- Detected 2026-11-07
- Disclosed 2026-11-10
- 3 days
Attack or cause
- Method
- [API abuse][Credential abuse]
- Impact
- [Data leak]
- Entry point
- Stolen credentials
- Affected, as stated
- 1
Data exposed or at risk
Services hit
Organizations involved
[Breached][Major]Osaka, Osaka, KitaInformation and communications
ILL
Sources
- [1][Official]当社提供の「CROSS POINT」への不正アクセスに関するお詫びと、緊急メンテナンスによるセキュリティ強化についてILL · 2026-11-10