Summary
- Environment: ARARA Message email delivery and cloud environments
- Operational impact: Email delivery suspended; restart date unresolved
- Financial impact: No confirmed incident cost quantified
- Record status: Developing record. Reviewed November 10, 2026; updated as evidence emerges.
What happened
ARARA confirmed data theft from its Message email-delivery service during October 28–31, 2026. Its third report added a second cloud environment to the same intrusion sequence. [2]
Impact
- ARARA reported 81,329,467 email addresses after removing overlap between categories. Some had associated attributes or text. These are addresses, not people; the maximum approximately 380 client companies includes both cloud environments. [2]
- SEGA disclosed 2,196,044 newsletter email-address records, including 92,273 with delivery information. This downstream subset must not be added to ARARA’s total. [1]
- SEGA and SEGA Fave newsletters were affected. SEGA excluded names, passwords, card information and SEGA Account emails, and had not confirmed misuse. [1]
Timeline
Initial disclosure
ARARA issued its first notice.
[2]Message service suspended
The company disabled environment B credentials and stopped the service.
[2]Revised total published
The third report reconciled overlapping address counts.
[2]SEGA reports newsletter impact
SEGA published its customer notice.
[1]Briefing updated
This briefing was last reviewed and updated on November 10, 2026.
Threat Group & Attack Vector
Environment B was entered using unauthorized credentials. ARARA corrected October 27 activity to suspected reconnaissance, with login and extraction beginning October 28. [2]
Actors
- No threat actor group has been identified in the reviewed public evidence.
TTPs
- T1078 — Valid Accounts: credentials enabled access to environment B. [2]
Response
ARARA’s response statement acknowledged suspicious emails sent through its service, regulator and police reporting, and an external investigation. Restart depended on remediation, safety checks and credential resets. [3]
SEGA paused affected newsletters and planned notices and joint regulator reporting. It explicitly distinguished the separate SEGA Fave arcade-server compromise. [1]
