依企業、國家、產業、發生年份和攻擊方式查詢事件，了解外洩資料、影響範圍、查證狀態、企業應對及來源。
After suspicious LINE messages on April 9, 2026, an April 17 update said LINE display names, clinic, campaign interest and some chat history may have leaked. Chart name/phone fields are not stored in that system.
Around March 5, 2026, the credit union’s third-party IT provider had a cybersecurity incident that allowed unauthorised actors to use its system to access AAGCU systems; files may have been accessed and copied.
An unauthorised third party gained access to certain systems; information may have been viewed or taken between October 6 and 7, 2025.
Possible data leak: AGS maintained the high-cost medical-care system and subcontracted to YCC. After YCC’s April 2, 2026 attack, city data held there was found on April 8; first notice April 17 and headcount on May 25.
Possible data leak: After the YCC file-server attack, the prefecture disclosed on April 17 that related data known as of April 16 had been stored on that server. No impact confirmed on live operational systems.
Possible data leak: After the April 2, 2026 YCC attack, build-contract data including ended contracts was found on the vendor server by April 16; disclosed April 17.
On March 20, 2024, Impac identified signs of unauthorised access; an unknown actor may have accessed files and folders with protected information between February 21 and March 20, 2024, including names and Social Security numbers.
Possible data leak: After Nippon Telenet (UPR subcontractor for car-share call centres) was attacked on March 9, 2026, UPR reported on April 13 and Nippon Rent-A-Car disclosed April 17. Rental-car members out of scope.
Possible data leak: After the April 2, 2026 YCC attack, core-system data including ended contracts was found on the vendor server by April 17.
Possible data leak: After the April 2, 2026 YCC attack, build-time data from the town and its designated manager was found on the hit server by April 17.
An unknown third party accessed certain Columbia Bank applications and information between October 2 and December 22, 2025; on March 6, 2026 the bank found the data contained personal information.
Unauthorised access to an employee’s Chatwork account may have exposed names, contacts and business/service-use information. No affected-person or record total was published.
On April 8, 2026 the tax office emailed the wrong FP-consultation list to another firm; noticed April 15 after one recipient opened then deleted it; disclosed April 16.
Possible data leak: After the April 2, 2026 YCC attack, a review through April 15 found city data including ended contracts still on the vendor server; disclosed April 16.
Fax contractor Nippon Telenet was attacked on March 9, 2026; on April 8 Cecile was told a Feb 24 fax-send backup may have been on the hit server and disclosed April 16.
On February 23, 2026, the firm discovered an unauthorised user had accessed its third-party tax filing software and filed fraudulent self-prepared returns on clients’ behalf; sensitive personal information was likely accessible to the actor.
Possible data leak: After the April 2, 2026 cyber-attack on YCC Information Systems, the town disclosed that its FY2016 care-prevention survey data had remained on the vendor’s server.
After seeing sales claims on an overseas site on April 11, 2026, STARTDASH found third-party access to an internal log console from April 1–6 and disclosed possible exposure of 39,267 users on April 14.
Around February 17, 2026, suspicious network activity was found; an unauthorised individual may have obtained files with customer names, addresses, dates of birth, diagnosis codes, insurance information and identification numbers.
On March 30, 2026, City Health discovered unauthorised access to its server that occurred between March 2 and 11, 2026; names, insurer names and procedure codes were accessed, but not dates of birth, contact details or SSNs.