
Cyber incident briefing
Arcadia breach put emergency-alert data and a trusted mail channel at risk
The Japanese provider says attackers exploited a media-server path-traversal flaw, obtained an internal service secret, reached authenticated sessions and used malicious code to send more than 1.4 million suspected phishing messages. The final data-loss scope remains under investigation.
What businesses need to know
Arcadia has confirmed unauthorized access across services used for mass notification and emergency communications, with possible exposure of contact and account-related data.1 Its latest incident page says the unauthorized mail ran from 1:17 a.m. to 7:16 a.m. Japan time on October 13 and totaled 1,423,428 messages; at least 869,575 went to addresses Arcadia says it did not hold.2
This is a supplier compromise, not evidence that every Arcadia customer lost data. Reported police figures are counts of people or addresses whose information may have been exposed, not a confirmed exfiltration count.46
How the intrusion unfolded
Arcadia’s October 19 technical report says a directory-path-traversal weakness on a media server exposed internal source files and a configuration file containing a secret used for service-to-service login. The company says the attacker used that secret while brute-forcing account IDs, then obtained internal information through authenticated sessions.3
The report describes database changes and a backdoor, but it does not name an attacker, identify a malware family, assign a CVE, or say whether the path-traversal weakness affected a third-party product. Those attribution and vulnerability details remain unestablished in the reviewed sources.3
- October 11: Arcadia’s reconstructed log begins at 6:26 a.m.; it records successful retrieval of a configuration file at 4:39 p.m. and says monitoring detected abnormal database load at 11:40 p.m.3
- October 12: Arcadia says it blocked the known access route at 3:00 a.m., changed a database password and later found that a WordPress plugin had been added.3
- October 13: The company says unauthorized mail started at 1:17 a.m.; it found a backdoor at 4:10 a.m. and stopped the mail at 7:16 a.m. It later shut down the affected
raiden3ands2services.3 - October 14–15: Investigators found traces of unauthorized access in NET119, legacy 119RAIDEN and an internal accounting subsystem. Arcadia says all services were restored by 3:10 p.m. on October 15.3
- October 21: Arcadia briefly restricted fax, broadcast-integration and file-attachment functions for additional checks, then said those restrictions were lifted at 7:30 p.m.2
Systems and data described by Arcadia
The numbers below come from Arcadia’s evolving notice. They measure different fields and systems, may overlap, and are framed by the company as maximum or possible exposure—not as a count of unique people or confirmed stolen records.2
| Service | Data described as possibly exposed | Published scale and boundary |
|---|---|---|
| SpeeCAN RAIDEN / RAIDEN School endpoints | Contact names, email addresses, phone and fax numbers, staff/contract information, and content retained in message history. | Arcadia’s preliminary maximum estimates were about 3.136 million email addresses, 105,000 phone numbers and 15,000 fax numbers. The company says payment-card data was not handled by SpeeCAN RAIDEN.2 |
| NET119 | Name, date of birth, sex, address, phone number, email address, fax number and information entered when registering for other services. | Arcadia later tied the possible exposure to data associated with 9,020 email addresses. It says sensitive personal information and video reports were not in the possible exposure it identified.2 |
119RAIDEN (fs119.ktaiwork.jp) |
Contact names, email, phone and fax numbers, staff/contract details, and content saved in message history. | About 97,000 email addresses, 17,000 phone numbers and 400 fax numbers were listed as possibly exposed. Arcadia excluded two other named 119RAIDEN endpoints after further review.2 |
What is known about the police data
Jiji Press reported, based on interviews with Japan’s National Police Agency, that information associated with about 125,000 officers and staff across 20 prefectural police forces may have been exposed. The reported fields were names and email addresses, with organizational affiliation recorded for some forces.4
The same reporting says four prefectural forces used Arcadia systems for public crime alerts, with roughly 16,000 individual names or addresses and 2,600 business or organizational addresses registered. FNN reported 22 prefectural forces affected across the two service categories; that overall count should not be read as 22 forces each having the same personnel exposure.45
These police totals are attributed reporting, not figures published in Arcadia’s technical report. At this reporting cutoff, the National Police Agency’s public “new arrivals” page did not show a matching Arcadia bulletin, so the police cohort should remain attributed to the news organizations and their NPA or police sources.8
How the phishing component worked—and what it does not prove
Arcadia says a malicious program used its environment to send messages that commonly resembled credit-card balance inquiries and were suspected phishing. The company’s October 21 update says at least 869,575 of the 1,423,428 messages went to addresses not held by Arcadia.23
That distinction matters: the send count is not a victim count, and it is not evidence that 1.4 million addresses were taken from Arcadia. The reviewed sources also do not establish how many messages arrived, were opened, led to credential entry or caused financial loss.
Reduce the risk from a compromised trusted sender
- Pause before acting on an alert. Treat unexpected payment, password, data-release or access-change requests as suspicious even when the sender name is familiar. Verify through a phone number or contact method already on file—not by replying or using a link or number in the message. CISA gives the same out-of-band verification advice for small and midsize businesses.7
- Map trusted communications suppliers. Record which vendors can send email, SMS, voice, fax or social posts in your name; who can disable each connection; and what alternate channel staff should use during an outage. This is practical guidance derived from the Arcadia incident, not a claim that your provider is compromised.
- Review logs before deleting evidence. If staff received a suspicious vendor-branded message, preserve the original message, headers, time, recipient and any security alerts before cleanup. Report it through your normal IT/security channel.
- Rotate only what exposure justifies. If a supplier directs customers to reset a password or reconnect an integration, use the supplier’s known official site and perform the change from a clean device. Do not infer that every credential or integration secret was exposed.
- Practice the fallback. Test how you would reach staff and customers if the primary alerting platform were unavailable. The goal is continuity, not proof that another platform is safer.
What remains unknown
- Which records were actually copied or removed, rather than merely reachable.
- The final number of unique people, organizations and data fields affected across overlapping Arcadia services.
- How the attacker first found the vulnerable path, how long any persistence existed, and whether more persistence or misuse will be identified.
- The attacker’s identity, motive and location; no named threat actor is established.
- Whether any phishing recipient submitted credentials or suffered financial loss.
- Whether the weakness has a CVE or affected third-party software; none is identified in the reviewed sources.
- Any U.S. or local-business exposure. The reviewed evidence identifies Japanese services and users and does not establish that a U.S. business was affected.
Reporting cutoff: October 21, 2026, 5:36 p.m. EDT (21:36 UTC). Arcadia describes the investigation as continuing, so exposure figures and remediation details may change.
Sources
| # | Source | Use and limitation |
|---|---|---|
| 1 | Arcadia corporate notice: 不正アクセスに伴う一連の対応について | Primary company confirmation and pointer to the living incident page. |
| 2 | SpeeCAN RAIDEN official incident page: 弊社サービスへの不正アクセスに伴う一連の対応について | Primary, continuously updated company account. Claims about scope and safety are Arcadia’s statements, not independent forensic findings. |
| 3 | Arcadia technical report: 不正アクセスの経過と当社の対処について (October 19) | Primary technical timeline and attack-chain description; investigation remained open. |
| 4 | Jiji Press: 警官・職員12.5万人分情報流出か | NPA-attributed reporting; possible exposure, not confirmed exfiltration. |
| 5 | FNN: 全国の警察官らの情報 大量流出か | Police-source reporting that distinguishes 22 forces overall from 20 using the staff safety-check service. |
| 6 | The Japan Times / Jiji: Data breach potentially exposes information of 125,000 police officers and staff | English-language Jiji report; not independent of Jiji’s Japanese report. |
| 7 | CISA: Teach Employees to Avoid Phishing | Primary U.S. government small-business guidance; not evidence about the Arcadia investigation. |
| 8 | National Police Agency: 新着情報 | Time-bounded check of the public release index; absence there does not prove the agency made no nonpublic statement. |
