Accellion data breach: Difference between revisions
m Archived references. |
→List of responses from affected organizations: some fixes |
||
| Line 19: | Line 19: | ||
==List of responses from affected organizations<!-- This contains only companies having any resemblance to consumers -->== | ==List of responses from affected organizations<!-- This contains only companies having any resemblance to consumers -->== | ||
Companies began being informed of the breach around January through March, later releasing | Companies began being informed of the breach around January through March, later releasing statement about the incident. Several companies decided to terminate their agreements with Accellion and collaborate with law enforcement and other companies, while also reaching out to potentially affected customers.<ref>{{Cite web |last=Panettieri |first=Joe |date=14 January 2022 |title=Accellion Vulnerabilities, Cyberattacks, Victims, Lawsuits: Customer List and Status Updates |url=https://www.msspalert.com/news/accellion-vulnerabilities-victim-list |url-status=live |archive-url=https://web.archive.org/web/20250711215300/https://www.msspalert.com/news/accellion-vulnerabilities-victim-list |archive-date=11 July 2025 |access-date=26 March 2026 |website=MSSP Alert}}</ref><ref>{{Cite web |last=Firch |first=Jason |date=14 May 2024 |title=Accellion Data Breach: What Happened & Who Was Impacted? |url=https://purplesec.us/breach-report/accellion-data-breach/ |url-status=live |archive-url=https://web.archive.org/web/20260416041503/https://purplesec.us/breach-report/accellion-data-breach/ |archive-date=16 April 2026 |access-date=26 March 2026 |website=Purplesec}}</ref> | ||
===Singtel=== | ===Singtel=== | ||
| Line 36: | Line 36: | ||
On 02 May, CXS made a statement highlighting the incident only leaking current and past employees personal information. The company didn't provide much details surrounding the incident in regards to customers or specific type of information, only saying “''To date, this incident has had no impact on business operations or our ability to serve our customers''".<ref>{{Cite web |date=2 March 2021 |title=CSX probes ‘security incident’ as hackers leak data |url=https://www.freightwaves.com/news/csx-probes-security-incident-as-hackers-leak-data |url-status=live |archive-url=https://web.archive.org/web/20260216050403/https://www.freightwaves.com/news/csx-probes-security-incident-as-hackers-leak-data |archive-date=16 February 2026 |access-date=27 March 2026 |website=FreightWaves}}</ref><ref>{{Cite web |last=Lester |first=David |date=3 March 2021 |title=CSX suffers data exposure by hackers |url=https://www.rtands.com/freight/csx-suffers-data-exposure-by-hackers/ |url-status=live |archive-url=https://web.archive.org/web/20240930080445/https://www.rtands.com/freight/csx-suffers-data-exposure-by-hackers/ |archive-date=30 September 2024 |access-date=26 March 2026 |website=RT&S}}</ref> | On 02 May, CXS made a statement highlighting the incident only leaking current and past employees personal information. The company didn't provide much details surrounding the incident in regards to customers or specific type of information, only saying “''To date, this incident has had no impact on business operations or our ability to serve our customers''".<ref>{{Cite web |date=2 March 2021 |title=CSX probes ‘security incident’ as hackers leak data |url=https://www.freightwaves.com/news/csx-probes-security-incident-as-hackers-leak-data |url-status=live |archive-url=https://web.archive.org/web/20260216050403/https://www.freightwaves.com/news/csx-probes-security-incident-as-hackers-leak-data |archive-date=16 February 2026 |access-date=27 March 2026 |website=FreightWaves}}</ref><ref>{{Cite web |last=Lester |first=David |date=3 March 2021 |title=CSX suffers data exposure by hackers |url=https://www.rtands.com/freight/csx-suffers-data-exposure-by-hackers/ |url-status=live |archive-url=https://web.archive.org/web/20240930080445/https://www.rtands.com/freight/csx-suffers-data-exposure-by-hackers/ |archive-date=30 September 2024 |access-date=26 March 2026 |website=RT&S}}</ref> | ||
===Centene=== | ===Centene === | ||
{{Incomplete section}} | {{Incomplete section}} | ||
| Line 47: | Line 47: | ||
On 24 March, [[wikipedia:Health_Net|Healthnet]], an American health care insurance provider, released a statement that declared customers addresses, date of birth, insurance ID number, and health information such as medical conditions and treatment information, was compromised. The company stated it started collaraborationg with law enforcement and cease operation of Accellion services.<ref>{{Cite web |date=24 March 2021 |title=Health Net received information that one of our business partners was a victim of a cyber-attack |url=https://www.healthnet.com/content/healthnet/en_us/news-center/news-releases/cyber-accellion.html |url-status=live |archive-url=https://web.archive.org/web/20210406205107/https://www.healthnet.com/content/healthnet/en_us/news-center/news-releases/cyber-accellion.html |archive-date=6 April 2021 |access-date=28 March 2026 |website=Health Net}}</ref> | On 24 March, [[wikipedia:Health_Net|Healthnet]], an American health care insurance provider, released a statement that declared customers addresses, date of birth, insurance ID number, and health information such as medical conditions and treatment information, was compromised. The company stated it started collaraborationg with law enforcement and cease operation of Accellion services.<ref>{{Cite web |date=24 March 2021 |title=Health Net received information that one of our business partners was a victim of a cyber-attack |url=https://www.healthnet.com/content/healthnet/en_us/news-center/news-releases/cyber-accellion.html |url-status=live |archive-url=https://web.archive.org/web/20210406205107/https://www.healthnet.com/content/healthnet/en_us/news-center/news-releases/cyber-accellion.html |archive-date=6 April 2021 |access-date=28 March 2026 |website=Health Net}}</ref> | ||
===The Reserve Bank of New Zealand=== | ===The Reserve Bank of New Zealand === | ||
{{Incomplete section}} | {{Incomplete section}} | ||
https://web.archive.org/web/20210111063645/https://www.rbnz.govt.nz/news/2021/01/reserve-bank-response-to-illegal-breach-of-data-system | https://web.archive.org/web/20210111063645/https://www.rbnz.govt.nz/news/2021/01/reserve-bank-response-to-illegal-breach-of-data-system | ||
| Line 82: | Line 82: | ||
==Consumer response== | ==Consumer response== | ||
{{Ph-I-ConR}} | {{Ph-I-ConR}} | ||