Reuters: Uber hacking investigation is concentrating on a Lyft exec
There’s little or no love misplaced between automotive-platform rivals Lyft and Uber. Nowhere is that extra obvious than in a Reuters’ article about nameless sources pointing fingers at Lyft’s know-how chief Chris Lambert because the possible explanation for an Uber hack. In line with the report, after a large breach of driver info again in February, Uber launched an investigation to find out who acquired into its system. That led it to courtroom to find out who was behind a Comcast IP handle that had accessed the safety key the journey-sharing firm by chance left on GitHub. Although the submitting attracts no connection to the precise hack (which based on Reuters sources was routed via a Scandinavian VPN) the courtroom dominated that the knowledge was “fairly doubtless” to assist the corporate discover the individual (or individuals) concerned within the breach.
Uber as an organization has not recognized Lambert. In reality the Comcast subscriber has remained nameless all through the courtroom proceedings. Nonetheless, it is fairly a leap to go from an IP handle that accessed a publicly out there file to outright hacking. The corporate believes that whereas there isn’t a direct connection between the thriller Comcast IP and the hack, the id of the individual behind that handle might shed some mild on the breach. Which is not all that far fetched.
Lance Cottrell, chief scientist of safety agency Ntrepid informed Engadget this sort of state of affairs is “attribute of the sort of errors individuals make when conducting an assault.” If the individual behind the IP tackle stumbled onto the important thing whereas perusing Uber’s GitHub account, it is already too late to start out hiding who they’re. It is often not till a nasty actor begins an precise assault that they take precautions like utilizing a VPN or public WiFi to cover their id. In fact that is if the nameless web consumer is definitely accountable.
Cottrell additionally stated we should always query the thoroughness by which Uber excluded different IPs. It is unclear what number of IP addresses hit the file, was within the tens or lots of? How did it decide if somebody was nefarious or not? Additionally, if the important thing was buried fairly deep within the firm’s GitHub web page, there is a good probability it wasn’t cached by Google. But when it wasn’t, Google might have cached the file and anybody might have grabbed it with out leaving a path.
In regards to the hypothesis that an Lyft worker might have had one thing to do with the breach, Lyft gave Engadget the next assertion: “Uber allowed login credentials for his or her driver database to be publicly accessible on GitHub for months earlier than and after a knowledge breach in Might 2014. We investigated this matter way back and there are not any information or proof that any Lyft worker, together with Chris, downloaded the Uber driver info or database, or had something to do with Uber’s Might 2014 knowledge breach.”
Uber declined to remark for this text.
[Image credit: Getty/AFP]