Leaked CROSS POINT API key exposed one customer’s membership data
I’LL confirmed unauthorized retrieval of member records through a customer-specific API key. It blocked the source and reissued API keys for all customers. The affected member count is unknown.
- Disclosed
- Nov 9, 2026
- Public disclosure date
- Severity
- Sharted
- No CVE: a breach, not a bug
- Splash zone
- One CROSS POINT customer’s member records were accessible through its leaked API key. Integrations using revoked keys require updates.
- CROSS POINT · API keys · data breach
- In the wild
- Yes
- I’LL confirmed that a third party used a leaked key to retrieve member data.
What happened
I’LL says the attacker used one customer’s legitimate API key after it leaked and obtained member data through the member information API. The vendor attributes the access to credential abuse and reports no direct database intrusion, tampering or software flaw. It found no signs of disclosure at other customers as of the notice. The affected organization, the number of member records and how the key leaked remain undisclosed.
The accessed data includes names, dates of birth, gender, postal and contact details, member numbers and tiers, points balances, in-store loyalty card numbers, online member IDs, and purchase statistics such as total spend, purchase counts and first or last purchase dates. The vendor says the affected system did not store payment-card data or login passwords. The product-wide key rotation applies to all customers and the confirmed data retrieval concerns one customer organization.
Crime-scene timeline
Nov 7, 2026
I’LL detects unauthorized API access in Japan
The vendor revokes and reissues the affected key and blocks the source. The detection date is in Japan time.
Nov 9, 13:15 UTC
Vendor completes reissuance for all customers
The vendor gives 22:15 Japan time and says it strengthened detection.
Nov 9, 23:31 UTC
Vendor publishes its investigation and response
The announcement is dated November 10 in Japan and confirms that one customer organization was affected.
Who said what
We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.
- I’LL CROSS POINT incident noticePrimaryConfirms abuse of a customer-specific key, the affected fields, all-customer key reissuance and continuing investigation.