Social Wire: flawed @Press API leaked member data; 41,981 records under investigation
A poorly protected internal API sent @Press member data, including hashed passwords, to a third party from 25 June to 28 October; 41,981 records are under investigation.
Disclosed
2026-11-02
Organizations involved
1
Leaked or at risk
42K
41,981
Downtime
Unknown
What happened
A check on 29 October found that part of an internal integration API of the @Press press-release service lacked proper authentication and access control. Logs show member data was sent to a third party through it. The unauthorized access ran from 25 June to 28 October. [1] [2]
It fixed the API and blocked the path the same day, and blocked connections from another path early on 30 October. No successful data retrieval has been recorded since. It disclosed the breach on 2 November. [1] [2]
Impact
The investigation covers 41,981 member records. The API handles company names, contact persons’ names and contact details, billing details, internal notes, login IDs and hashed passwords. Responses were not logged, so what was taken for each member cannot be fully established. No account takeover or unauthorized release distribution has been found. [1] [2]
Response
Timeline
- Started 2026-06-25
- Detected 2026-10-29
- Disclosed 2026-11-02
- 130 days
Attack or cause
- Method
- [API abuse]
- Impact
- [Data leak]
- Entry point
- API
Data exposed or at risk
Services hit
Organizations involved
[Breached][Critical]Tokyo, MinatoInformation and communications41,981 leaked
Social Wire
Sources
- [1][Official]「@Press」への不正アクセスに関するお知らせSocial Wire · 2026-11-02
- [2][Official]【重要】@Pressへの不正アクセスに関するお知らせと、パスワード再設定のお願いSocial Wire · 2026-11-02