Marimo Holdings: group employee data leaked after officer-impersonation phishing
On December 18, 2025 a phishing mail impersonating a group officer led to unauthorised acquisition of some employee data including leavers; disclosed March 6, 2026.
依企業、國家、產業、發生年份和攻擊方式查詢事件,了解外洩資料、影響範圍、查證狀態、企業應對及來源。
On December 18, 2025 a phishing mail impersonating a group officer led to unauthorised acquisition of some employee data including leavers; disclosed March 6, 2026.
On February 2, 2026, EP Wealth discovered unauthorised activity on its network involving one employee’s compromised credentials and terminated it within hours; the unauthorised party obtained copies of data, including from client relationship tools.
On February 9, 2026 one staff mailbox was taken over via phishing and sent 321 suspicious messages; the campus disclosed on March 6 that mailbox personal data may have been viewed.
On August 23, 2025, the firm was advised of possible unauthorised access to its network; the investigation confirmed unauthorised access to a portion of the network on that day, followed by a review of the files there.
Tieu Dental became aware of unauthorised access to its network; the forensic investigation found the actor accessed the network between July 28 and 29, 2025, and personal and/or health information may have been accessed or acquired.
Possible data leak: Malicious code on the e-commerce site potentially captured card numbers, expiry dates and CVV codes for purchases from about March 12 to September 16, 2025.
On December 30, 2025, the firm discovered an unauthorised third party had accessed its network; the investigation found files were acquired from certain systems on December 25 and 26, 2025.
On December 12, 2025, CFPA learned that certain personal information had been inadvertently disclosed to an unknown third party that day; only individual broker information was affected, not policyholder data (except brokers who are also policyholders).
On January 21, 2026, an attack resulted in unauthorised read-only access to some backup systems, including limited access to users’ basic account details (metadata, contact details, usernames, dates of birth and names).
Possible data leak: After a third-party report that a staff device screen was visible on public transport on February 27, 2026, the firm investigated and disclosed on March 3.
A bulk admin email used To instead of Bcc so addresses were visible among recipients; AMED disclosed this on March 3, 2026.
Investigation of an August 3, 2025 network disruption found an unknown actor accessed and acquired data.
Possible data leak: On February 17, 2026 a leftover test file on production was found and closed the same day; disclosed March 3, with an April 17 update reporting no further intrusion traces.
On November 25, 2025, M&Y identified suspicious activity on a server used for historical record keeping; the investigation found an unknown actor viewed and downloaded files on or about November 23, 2025.
A document was intermixed with another claimant’s information and emailed to that claimant, disclosing name, Social Security number and work-injury medical information.
Exploitation of a then-unknown Oracle E-Business Suite vulnerability allowed a third party to access and obtain files from Maritz’s finance environment on August 10–13, 2025.
Possible data leak: Activity in the website environment from January 25 to 28, 2026 may have involved personal information.
On October 31, 2025, an unauthorised party accessed a third-party file-hosting system, affecting names, contact details and other fields.
An unauthorised person accessed data from the vendor-hosted Oracle E-Business Suite in August 2025; hiring and payment records included names and SSNs.
A compromised cloud-mail account may have allowed viewing or acquisition of address-book email addresses. Sending suspicious phishing emails is confirmed; data acquisition is not.