Uber: Difference between revisions

From Enlace Hacktivista
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
(One intermediate revision by the same user not shown)
Line 6: Line 6:
From there, the attacker accessed several other employee accounts which ultimately gave the attacker elevated permissions to a number of tools, including G-Suite and Slack. The attacker then posted a message to a company-wide Slack channel, which many of you saw, and reconfigured Uber’s OpenDNS to display a graphic image to employees on some internal sites.
From there, the attacker accessed several other employee accounts which ultimately gave the attacker elevated permissions to a number of tools, including G-Suite and Slack. The attacker then posted a message to a company-wide Slack channel, which many of you saw, and reconfigured Uber’s OpenDNS to display a graphic image to employees on some internal sites.


* Source: https://web.archive.org/web/20220921070053/https://www.uber.com/newsroom/security-update/
== Media Coverage ==
== Media Coverage ==
* https://www.itpro.com/security/369091/uber-hack-started-with-smishing-social-engineering-attack
* https://www.itpro.com/security/369091/uber-hack-started-with-smishing-social-engineering-attack

Latest revision as of 00:53, 23 September 2022

Ride-share giant Uber confirmed that it was responding to “a cybersecurity incident” after TeaPot claimed to have hacked Uber. A hacker calling themselves "Tea Pot" claims to be the individual who took responsibility for the attack, bragging to multiple security researchers about the steps they took to breach the company.

Explanation of the Hack

An Uber EXT contractor had their account compromised by an attacker. It is likely that the attacker purchased the contractor’s Uber corporate password on the dark web, after the contractor’s personal device had been infected with malware, exposing those credentials. The attacker then repeatedly tried to log in to the contractor’s Uber account. Each time, the contractor received a two-factor login approval request, which initially blocked access. Eventually, however, the contractor accepted one, and the attacker successfully logged in.

From there, the attacker accessed several other employee accounts which ultimately gave the attacker elevated permissions to a number of tools, including G-Suite and Slack. The attacker then posted a message to a company-wide Slack channel, which many of you saw, and reconfigured Uber’s OpenDNS to display a graphic image to employees on some internal sites.

Media Coverage