A data breach on DEA's Law enforcement system reportedly granted administrators of doxxing and swatting website Doxbin and linked to Lapsus$ hacking group access to at least 16 databases.
Security incidents happen; that’s just reality. But how a company decides to handle an event says more about their values and priorities than their product. The recent Okta compromise reminds us of the damage inflicted when there is a lack of transparency between a security vendor and its customers.
Data breach on Cash App Investing platform exposed customer information of 8.2 million users in the U.S. after a former employee downloaded customer reports.
Globant SAS confirmed a data breach affecting a "limited" number of customers after Lapsus$ hackers published 70GB of source code allegedly stolen from the company. Screenshots suggested that the leaked customer source code belonged to companies like Apple, Facebook and DHL.
Lapsus$ hackers compromised Microsoft's Azure DevOps Server, exfiltrated and published source code for the company's web infrastructure, websites, and mobile apps.
Where there is data, there is a risk of a data breach. It is essential to implement protective measures for such an event and to educate oneself to spot a potential breach.
Samsung says that no personal information was lost in the data breach and that it does not expect customers to be impacted, but the source code could lead to serious vulnerabilities.
Manila Bulletin, the largest English-language newspaper in the Philippines, says that a serious data breach of the country's Commission on Elections (Comelec) occurred. Comelec called it "fake news" and claimed that it never happened.
FlexBooker, a commonly used appointment scheduling and calendar service, is apologizing to its customers after 3.7 million records appeared on a dark web hacker forum following a DDoS attack.
Cox communications data breach notification disclosed that unauthorized individual(s) accessed sensitive customer information after impersonating the company's support agent.