AXA Direct Japan disclosed unauthorised access to its MyAXA customer portal and to Prestige Core Solution, an outsourced roadside-assistance provider, in a second report published on 13 November 2026. About 597,000 MyAXA accounts may have been affected, and the data that may have been exposed includes names, addresses, dates of birth, email addresses and telephone numbers. The company confirmed that unauthorised access to, and leakage of, some customer information did take place, and stated that credit card information was not included for MyAXA. No misuse of the information had been confirmed as of the disclosure. AXA Direct Japan is the Japanese general insurance arm of AXA, and MyAXA is its customer portal, where policyholders manage their insurance online. The company published a first report on 12 November 2026 and a fuller second report on 13 November 2026, and AD HOC NEWS summarised the disclosure in English on 13 November 2026.
How the intrusion unfolded
On 9 November 2026, AXA Direct Japan detected suspicious access to MyAXA at about 08:30 and blocked the access at 10:53 the same morning. The investigation then confirmed that a third party had accessed customer information without authorisation. The company suspended the related web services after detecting the access, and restored MyAXA on 12 November 2026 after confirming its safety. The first report, published on 12 November 2026, confirmed the unauthorised access and stated that the cause and the extent of the impact were still being investigated. The second report, published on 13 November 2026, added the number of accounts that may have been affected, the types of data involved, and the details of the second incident at the roadside-assistance provider.
The second incident has a separate timeline. Prestige Core Solution, the company to which AXA Direct Japan outsources part of its roadside-assistance work, detected unauthorised access to its own systems on 29 October 2026. On 2 November 2026, it told AXA Direct Japan that some AXA customer information held by the provider had been taken outside its systems. AXA Direct Japan has not published a count or a list of data types for the Prestige side. The range of customers affected and the information involved are still being examined, and the company stated that it will report further details when they are known.
Records in scope
The second report lists five items of MyAXA data that may have been exposed: customer names, addresses, dates of birth, email addresses and telephone numbers. The count attached to that list is about 597,000 accounts, described by the company as the number that may have been affected. The notice confirms that unauthorised access to some customer information, and leakage of some of that information, did take place. It does not state that all 597,000 records were taken, so the 597,000 figure is the population at risk, not a confirmed exfiltration count. The company is still identifying the affected customers and confirming the details, and stated that it will contact affected customers individually as confirmation proceeds.
The five data types together are the material for impersonation. A name, address, date of birth, email address and telephone number allow a message to address the recipient by name and quote real personal details, and the email address provides the channel for sending that message. A message that claims to come from AXA Direct Japan, a bank or a delivery company can be checked against the company's own published notices rather than trusted on its own wording. The phishing guide describes how a leaked email address is used after a breach: the address becomes the target list, and the other leaked details become the material that makes each message convincing.
Data not mentioned in the notice
AXA Direct Japan stated in the second report that credit card information was not included in the MyAXA data. That exclusion applies to the MyAXA side of the incident. The notice does not mention passwords at all. It neither states that passwords were exposed nor states that they were not, so no claim about MyAXA passwords can be made either way until the company says more. Policy numbers and bank account details are also not listed in the MyAXA notice.
The Prestige side is separate from the MyAXA side on this point. Prestige International, the parent company of Prestige Core Solution, disclosed on 2 November 2026 that up to about 5.5 million records across its clients may have been taken, a maximum that includes duplicate records, with the number of unique people still under review. That figure covers all of Prestige's clients, not AXA alone, and it is not an AXA number. Japan Cyber Watch reported that the Prestige records include names, addresses, phone numbers, email addresses, vehicle registration and chassis numbers, accident and breakdown details, and bank account information for some people. Prestige's second report, on 6 November 2026, added that credit card numbers of three people had been taken, written into reception records. Those card numbers belong to the Prestige-wide incident, not to AXA specifically, and AXA's own statement that credit card information was not included applies to MyAXA.
The Prestige incident
Prestige Core Solution runs the roadside-assistance system. It takes calls and dispatches help on behalf of insurers, car leasing companies and others. Prestige International detected unauthorised access to the group business system on 29 October 2026. It revoked the credentials that had been misused. The access continued, so the company stopped the system on 30 October 2026. Roadside assistance has continued through alternative operations since then. The company is investigating with outside specialists. It is reporting to Japan's Personal Information Protection Commission and consulting the police.
AXA Direct Japan is one of several clients that have disclosed their exposure through Prestige. Sony Assurance, ENEOS, Nippon Car Solutions and Sompo Japan have each published their own notices, with different figures and different levels of detail. ENEOS put its exposure at up to 8,500 contracts. Sompo Japan put its figure at about 65,000 records. Nippon Car Solutions passed on what Prestige told it about the cause: flaws in the web application's access control and in how credentials were managed. That cause statement concerns Prestige, and it is not the cause of the MyAXA intrusion, which AXA Direct Japan has not explained. The customers affected through Prestige did not choose the contractor. They bought car insurance or a lease, and the company behind the roadside desk was a supplier to the company they bought from.
Company response and service status
AXA Direct Japan's response, as described in the second report, covers five actions: blocking the unauthorised access route into MyAXA and applying the necessary security measures, strengthening monitoring for unauthorised access, investigating the cause and the extent of the impact, stopping customer-data transfers to Prestige Core Solution and working with the provider on containment, and reporting to the relevant authorities and cooperating with them. The first report also warned customers to be careful about suspicious contacts, and not to open suspicious links in email or SMS messages or to enter passwords and authentication codes in response to them.
MyAXA is back in service. It was restored on 12 November 2026 after the company confirmed its safety. Some web functions for the roadside-assistance service provided by Prestige remain suspended. Roadside assistance itself continues by telephone and through alternative operating procedures, so drivers who need help can still reach it. The company has published contact points for customers. The MyAXA contact centre can be reached on 0120-999-935, and a separate line, 0120-975-986, covers roadside assistance. Affected customers are to be contacted individually as the company confirms who is affected.
What MyAXA customers can do
AXA Direct Japan advised customers to be careful about suspicious contacts and not to open links in email or SMS messages or enter passwords and authentication codes in response to them. Customers who use MyAXA should change their MyAXA password. Changing a password after a breach closes the most direct route an attacker could take with the exposed data, and any other account that shares the MyAXA password should get a new, different password as well. Customers should also expect messages that use the leaked details. A message that quotes a real name, address and date of birth can look genuine, so links in unexpected messages should not be opened, and passwords and authentication codes should not be entered through a link in a message. The what to do after a breach guide sets out the steps in order: check whether the address appears in known breaches, change the passwords on the affected accounts, and then limit the damage the next leak can do. Have I Been Pwned is the reference database for the first step.
Your address is probably in this file. Check whether it is, do the password work above, and then fix the part you control: the address you hand out next time. One AliasFleet alias per service means the next leak can only point back to the service that leaked it. Founders Club is $7 a month, locked forever, instead of $12. Early members only.
Where the investigation stands
The investigation is still open on both parts of the incident. AXA Direct Japan stated that the cause of the unauthorised access and the full extent of the impact are still under investigation, and that no misuse of the information or secondary damage had been confirmed as of 13 November 2026. The Prestige side is further from resolution: the range of AXA customers affected through the provider and the information involved are still being examined, with no AXA-specific figures published yet. Three facts are still missing. The first is how many of the 597,000 MyAXA accounts had data actually taken, rather than merely put at risk. The second is how the attacker reached MyAXA, which the company has not explained. The third is the AXA-specific scope of the Prestige incident. Until those facts are published, the description of the incident is the company's own: about 597,000 accounts may have been affected, some leakage is confirmed, no misuse has been confirmed, and the investigation continues.
Top comments (0)