Microsoft indicates increased risk of Office 365 phishing by Oauth Apps #Consentphishing

While world moving with the shift of remote working , customer's are exposed to additional risk and threat actor take advantage of new attack vector like consent phishing with the old attack vendor like conventional credential theft and phishing attacks

Consent phishing: An application-based threat to keep an eye on

Today developers are building apps by integrating user and organizational data from cloud platforms to enhance and personalize their experiences. These cloud platforms are rich in data but in turn have attracted malicious actors seeking to gain unwarranted access to this data. One such attack is consent phishing, where attackers trick users into granting a malicious app access to sensitive data or other resources. Instead of trying to steal the user’s password, an attacker is seeking permission for an attacker-controlled app to access valuable data.
While each attack tends to vary, the core steps usually look something like this:

1.     An attacker registers an app with an OAuth 2.0 provider, such as Azure Active Directory.
2.     The app is configured in a way that makes it seem trustworthy, like using the name of a popular product used in the same ecosystem.
3.     The attacker gets a link in front of users, which may be done through conventional email-based phishing, by compromising a non-malicious website, or other techniques.
4.     The user clicks the link and is shown an authentic consent prompt asking them to grant the malicious app permissions to data.
5.     If a user clicks accept, they will grant the app permissions to access sensitive data.
6.     The app gets an authorization code which it redeems for an access token, and potentially a refresh token.
7.     The access token is used to make API calls on behalf of the user.

If the user accepts, the attacker can gain access to their mail, forwarding rules, files, contacts, notes, profile and other sensitive data and resources.

An image of a Consent screen from a sample malicious app named “Risky App."

How to protect your organization

Check for poor spelling and grammar. If an email message or the application’s consent screen has spelling and grammatical errors, it’s likely to be a suspicious application.
    Keep a watchful eye on app names and domain URLs. Attackers like to spoof app names that make it appear to come from legitimate applications or companies but drive you to consent to a malicious app. Make sure you recognize the app name and domain URL before consenting to an application.
    Promote the use of applications that have been publisher verified. Publisher verification helps admins and end-users understand the authenticity of application developers. Over 660 applications by 390 publishers have been verified thus far.
    Configure application consent policies by allowing users to only consent to specific applications you trust, such as application developed by your organization or from verified publishers.

Source