Consent phishing

Consent phishing is deception that persuades someone to grant a malicious application permissions to access data or services.

The dangerous step is approving the app

An attacker gives someone a believable reason to approve application access, such as permission to read files. The person can sign in through the real identity provider and still grant access to an unwanted app.

The app’s identity and requested permissions matter here. A genuine approval page does not establish that the app belongs in your environment.

How it differs from credential phishing

Credential phishing tries to obtain a sign-in secret. Consent phishing seeks an authorization grant. The attacker may never learn the user’s password.

In Entra, user-consent policy can limit what an employee may approve, while some permissions require admin consent. The review should match the app’s permissions to its intended job.

Removing an unwanted grant

In Microsoft Entra, identify the app and service principal, approver, permission type, affected users, and consent record. Compare the permissions with the claimed task, then review activity logs for use of that access. A grant shows what was approved; it does not show which files were downloaded.

Microsoft’s response playbook covers investigating illicit grants and disabling malicious apps. A password change does not remove an app’s consent grant. Have the identity or application administrator choose the containment steps and check the result.

Other platforms handle app authorization differently. The UNC6040 campaign analysis covers a Salesforce example; Entra procedures cannot be applied unchanged.

Sources

See it in practice