Skip to content
JAENES
APossible leakOctober 8, 2026 announced

オリックス生命(業務委託先スカラコミュニケーションズのFAQシステム「i-ask」)Data breach / unauthorized access incident

笹尾 祐太朗の写真Reviewed by Yutaro SasaoWritten by Leak Watch editorial team published ・ updated
Occurred on
October 2, 2026
Announced on
October 8, 2026
Severity
AFinancial and HR records — information that easily translates into monetary damage.
Scale
26,500 records
Main impact
Due to unauthorized access to the admin site of the FAQ system “i-ask” operated by subcontractor スカラコミュニケーションズ, it was disclosed that about 26,500 records (total counts including multiple inquiries by the same customer) of names, dates of birth, addresses, phone numbers, email addresses, policy numbers, inquiry contents, and medical information reported by customers may have been exposed. My Number and credit card numbers were not affected. The incident was detected by a monitoring alert on the morning of October 3 and was blocked and isolated the same day; individual notifications to potentially affected customers and an investigation by external specialists are underway.
Information involved
Full nameDate of birthHome addressPhone numberEmail addressUser / member IDHealth & medical data
Cause / key point
Unauthorized login by a third party to the outsourced FAQ system “i-ask” admin site and installation of malicious software (2026-10-02 20:30 approx. to 2026-10-03 08:00 approx.); password changes and isolation were implemented.About Abuse of credentials
Industry
Finance & insurance
Listing / capital
UnlistedParent company (listed holding company): オリックスホールディングス(TSE Prime 8591)

The incident entity, オリックス生命保険株式会社, is unlisted and is under オリックスホールディングス (TSE Prime・8591).

Last updated
October 29, 2026

Stock price reaction to the disclosureオリックスホールディングス・親会社(上場持株会社) / 東証プライム 8591

2026.09.18 〜 2026.10.29Loading…

Stock information is reference data based on Yahoo Finance and may be delayed. This site does not solicit or advise investment and does not guarantee the accuracy or completeness of this information. We accept no liability for any investment decision based on it.

Where to go for this information

The steps themselves are on the protection guide. These links match the kinds of data in this incident, plus support contacts.

Ask AI about this incident

Opens an AI chat with this page's URL already in the prompt. Treat the answer as a starting point — always verify with the official sources listed above.

Ask ChatGPT ↗Search Perplexity ↗

Full nameDate of birthHome addressPhone numberEmail addressUser / member IDHealth & medical dataHow severity is assessed →

Is this incident worth paying attention to?

Written & reviewed

笹尾 祐太朗の写真

Reviewed byYutaro SasaoFounder & CEO, MediaLeap Inc.

CEO of MediaLeap Inc. Working on both sides of web advertising and web media since 2013; founded the company in May 2025.

Review scope: cross-checking against primary sources (official and government announcements), verifying claims stay within the facts, and checking source attribution。Last reviewed:

Written by:Leak Watch editorial team (AI-assisted drafts verified against sources by the editorial team) · Reviewer profile · Request a correction

Related incidents

Browse the database →

Incidents sharing the same company, service, attack method or industry (grouped automatically from the disclosures).

Incidents related to "クレジットカード"

Incidents where the damage spread through the same service or system.

Incidents related to "プログラム"

Incidents where the damage spread through the same service or system.

Same attack method

Same industry

Attack method classification: Abuse of credentials(Logging in legitimately with leaked or guessed passwords)

Read the Abuse of credentials guide and national trends →

← Back to Breach Watch