The threat group called Lapsus$, which has been hitting companies all over the globe, said it gained access to the source code of Microsoft products such as Bing and Cortana. After they attack, the group said it leaked nearly 40 Gb of files.
In terms of the Okta breach, scope remains unclear, but it could have major consequences because thousands of companies rely on San Francisco-based company to manage access to their networks and applications.
Okta Chief Security Officer David Bradbury said in a blog post a customer support engineer working for a third-party contractor had his computer accessed by the hackers for a five-day period in mid-January and “the potential impact to Okta customers is limited to the access that support engineers have.”
Some Impact
“There are no corrective actions that need to be taken by our customers,” he said.
Nevertheless, Bradbury said support engineers were able to help reset passwords and some customers “may have been impacted.” He said the company was in the process of identifying and contacting them.
“After a thorough analysis of these claims, we have concluded that a small percentage of customers – approximately 2.5 percent – have potentially been impacted and whose data may have been viewed or acted upon,” Bradbury said in an updated post. “We have identified those customers and are contacting them directly. If you are an Okta customer and were impacted, we have already reached out directly by email. We are sharing this interim update, consistent with our values of customer success, integrity, and transparency.”
The nature of that impact wasn’t clear and Okta did not immediately say how many organizations were potentially affected or how that squared with Okta’s advice that customers did not need to take corrective action.
On its website, Okta describes itself as the “identity provider for the Internet” and says it has more than 15,000 customers on its platform.
It competes with the likes of Microsoft Corp, PingID, Duo, SecureAuth and IBM to provide identity services such as single sign-on and multifactor authentication used to help users securely access online applications and websites.
Internal Communications Published
Okta’s statement follows the posting of a series of screenshots of Okta’s internal communications by a group of ransom-seeking hackers known as Lapsus$ on their Telegram channel late on Monday.
In an accompanying message, the group said its focus was “ONLY on Okta customers.”
Lapsus$ responded to Okta’s statement on Tuesday by saying the company was trying to minimize the importance of the breach.
In the attack against Microsoft, the software giant said in a blog post:
“This week, the actor made public claims that they had gained access to Microsoft and exfiltrated portions of source code. No customer code or data was involved in the observed activities. Our investigation has found a single account had been compromised, granting limited access. Our cybersecurity response teams quickly engaged to remediate the compromised account and prevent further activity. Microsoft does not rely on the secrecy of code as a security measure and viewing source code does not lead to elevation of risk. The tactics DEV-0537 (the name Microsoft uses for Lapsus$) used in this intrusion reflect the tactics and techniques discussed in this blog. Our team was already investigating the compromised account based on threat intelligence when the actor publicly disclosed their intrusion. This public disclosure escalated our action allowing our team to intervene and interrupt the actor mid-operation, limiting broader impact.”

