Explore

Identity-Based Cyberattacks: Why Credential Theft Is a Business Risk

Published by: Gautham Krishna RNov 20, 2026Blog
blog_image

For years, cybersecurity conversations centred on malware, firewalls, and phishing emails with obvious warning signs. That focus is no longer sufficient. Attackers have learned that a valid username and password-or a stolen session token-can open more doors than a piece of malicious software, with less noise and less risk of detection.

The numbers reflect this shift. Verizon's 2025 Data Breach Investigations Report found that stolen credentials were involved in 32% of breaches, making them one of the most common paths into an organisation. Microsoft's Digital Defense Report 2025 reported that identity-based attacks rose 32% in the first half of 2025 alone, with more than 97% of those attacks being large-scale password attacks. CISA and the FBI have issued advisories naming identity abuse-stolen credentials, MFA bypass, session hijacking, and OAuth abuse-as a dominant initial access vector.

Phishing remains one way credentials are obtained. But the broader problem is identity: how employees prove who they are, what they are allowed to access, and how attackers exploit legitimate permissions once they are inside. This article explains how identity-based cyberattacks work, why they create serious business risk, and what organisations can do to reduce exposure.

What Are Identity-Based Cyberattacks?

Identity-based cyberattacks are attacks that compromise or misuse an employee's identity-their credentials, session, authentication factors, or application permissions-to access business systems. The attacker does not necessarily break through a network perimeter. They log in.

This distinction matters. A compromised identity can provide access to email, cloud storage, finance systems, HR platforms, and connected third-party applications. The attacker operates within the permissions granted to that account, which means activity can blend into normal business operations. Verizon describes stolen credentials as valuable precisely because they "unlock all the doors," allowing criminals to move around a system undetected.

Identity-based attacks are not a single technique. They include credential theft, account takeover, business email compromise, MFA fatigue, session hijacking, OAuth abuse, and privileged account compromise. Each exploits a different part of the identity and access chain.

Common Types of Identity-Based Cyberattacks

Credential Theft and Account Takeover

Credential theft is the acquisition of usernames, passwords, or authentication secrets. Common methods include phishing, infostealer malware, credential stuffing using passwords leaked in previous breaches, and fake login pages. Once credentials are stolen, account takeover follows: the attacker logs in as the employee and inherits that account's access.

Verizon's 2025 DBIR found that credential abuse was an initial access vector in 22% of breaches, the single most common entry point. Infostealers-malware designed to harvest passwords, session tokens, and browser data-compromised 30% of corporate devices and 46% of unmanaged devices in the report's dataset. After takeover, an attacker can read email, download files, change passwords, and in some cases lock the legitimate user out.

Business Email Compromise (BEC)

Business email compromise is a form of identity-based fraud in which an attacker gains access to, or convincingly impersonates, a legitimate business email account to manipulate payments or data. Common patterns include invoice fraud, payment redirection, executive impersonation, and fraudulent instructions to finance or HR teams.

BEC can succeed without malware. In January 2023, a workers union in Dorchester, Massachusetts, was defrauded of $6.4 million after receiving a spoofed email that appeared to come from its investment manager. The email directed the union to transfer funds to a different bank account controlled by a third party. The U.S. Department of Justice later secured forfeiture of over $5.3 million traceable to the scheme. The lesson is not that email is inherently insecure, but that trust in a familiar sender or instruction can be exploited when verification procedures are absent.

MFA Fatigue and Push Bombing

Multi-factor authentication is an important control, but it is not a complete solution. MFA fatigue-also called push bombing-occurs when an attacker who already has a valid password repeatedly triggers authentication prompts on the employee's device until the employee approves one out of confusion, annoyance, or exhaustion.

A joint CISA and FBI advisory, updated in 2025, names push bombing as one of the most common ways attackers bypass multi-factor protections. The threat group known as Scattered Spider has built a playbook around this technique, combining repeated MFA prompts with help-desk impersonation to reset credentials. CISA's advisory on Scattered Spider documents the group sending repeated MFA notification prompts that lead employees to press "Accept".

Microsoft reports that phishing-resistant MFA can prevent up to 99% of identity attacks, yet the report also acknowledges that accounts with MFA enabled are still taken over. The conclusion is not that MFA is ineffective, but that the type of MFA matters. Push-based approval is more susceptible to fatigue than phishing-resistant methods such as FIDO2 security keys or passkeys.

Session Hijacking and Token Theft

Session hijacking bypasses the login process entirely. When a user authenticates, the application issues a session token or cookie that keeps them logged in. If an attacker steals that token-through infostealer malware, adversary-in-the-middle phishing, or other means-they can replay it and impersonate the already-authenticated user without needing the password or a new MFA prompt.

Microsoft's 2025 report notes that infostealer malware is now routinely used to steal session tokens directly from a browser, allowing an attacker to skip the MFA prompt because they are impersonating an already logged-in session. This is a critical distinction: credential theft targets the password; session hijacking targets the proof that authentication already happened. Defences must address both.

OAuth and Cloud Account Abuse

OAuth is an authorisation framework that lets a user grant a third-party application limited access to their account-for example, allowing a calendar app to read email metadata or a project tool to access files. OAuth is not authentication; it is permission delegation. Attackers abuse it through consent phishing, where a user is tricked into granting a malicious application access to their Microsoft 365 or Google Workspace account.

Consent phishing campaigns affected 900 tenants and 3,000 user accounts in 2025, with one campaign creating 17,000 malicious apps and sending 927,000 messages. The attack is effective because the consent screen is legitimate-it appears on the real Microsoft or Google domain-and the permissions requested may include read and write access to email, contacts, and files. Access tokens obtained through OAuth can persist even after a password reset, which means traditional credential-focused controls may not remove the attacker's access.

The ConsentFix technique takes this further: if a user is already logged into an application in their browser, attackers may not need credentials or an MFA check at all-only the user's action of copying and pasting. Organisations should review connected applications, consent permissions, and token lifetimes, not only password policies.

Privileged Account Compromise

Privileged accounts-administrator accounts, service accounts, and accounts with elevated access-are attractive targets because compromising one can provide broad control over systems and data. Excessive permissions increase the blast radius of any compromise. Shared administrator credentials and inactive accounts that retain privileges create additional risk.

Least privilege, privileged access management, and periodic access reviews are established controls for reducing this exposure. The goal is not to eliminate administrative access, but to ensure that elevated access is limited, monitored, and removed when no longer needed.

Why Are Identity-Based Attacks Dangerous for Businesses?

The business impact of identity compromise extends beyond the technical breach. Unauthorised access to email and cloud applications can expose customer data, employee records, financial information, and strategic communications. BEC and payment redirection can cause direct financial loss. Compromised accounts can be used to send further phishing emails to colleagues, customers, and partners, extending the attacker's reach.

Lateral movement is a particular concern in cloud environments. An initial compromised account may have permissions that allow access to shared files, connected applications, and collaboration platforms. Attackers can use that access to identify additional targets and escalate privileges. Operational disruption follows when accounts are locked, sessions revoked, or systems taken offline during investigation. Reputational damage and incident response costs compound the financial impact.

The distinction between a technical attack and its business consequence is important. A stolen session token is a technical event. A fraudulent payment authorised through a compromised executive account is a business outcome. Security controls must address both the access pathway and the business process that the access enables.

How Attackers Exploit Legitimate Access: An Illustrative Scenario

The following is an illustrative scenario, not a documented incident. It shows how a single compromised identity can provide access across connected systems.

An employee in a finance team receives an email that appears to be from a known vendor, referencing a recent invoice. The email contains a link to a document that requires "signing in with Microsoft 365" to view. The employee enters their credentials and completes an MFA prompt. The login page was a phishing proxy; the credentials and session token are captured.

The attacker now has a valid session. They access the employee's email, identify an ongoing payment thread with a supplier, and send a follow-up email from the employee's account instructing the supplier to use updated bank details. They also review shared files for other payment approvals and identify a colleague in accounts payable who has authority to approve larger transfers. The attacker sends a similar credential-harvesting email to that colleague, this time from the compromised internal account, which makes the message more credible.

No malware was installed. No vulnerability was exploited. The attack relied on legitimate access obtained through a compromised identity. The controls that would have reduced the risk include phishing-resistant authentication, out-of-band verification for payment changes, monitoring of unusual session activity, and least-privilege access that limited what the compromised account could reach.

How Businesses Can Prevent Identity-Based Cyberattacks

Strengthen authentication. Multifactor authentication should be deployed everywhere, but the type matters. Phishing-resistant MFA-FIDO2 security keys and passkeys-is significantly harder to fatigue, phish, or replay than push notifications or SMS codes. Number matching reduces the effectiveness of push bombing. Privileged and finance accounts should be prioritised for phishing-resistant methods.

Apply least privilege and review access. Employees should have only the permissions required for their role. Service accounts and administrator accounts should not be used for everyday email and browsing. Periodic access reviews should identify dormant accounts, excessive permissions, and shared credentials.

Monitor sessions and tokens, not only logins. Detection should flag unusual session activity, impossible travel, token replay from unexpected locations, and changes to MFA methods. Centralised logs that correlate identity events with financial transactions improve the chance of catching an attack before a payment is made.

Review OAuth permissions and connected applications. Organisations should inventory third-party applications with access to Microsoft 365, Google Workspace, and other cloud platforms. Consent policies should restrict which applications users can approve. Tokens and permissions should be reviewed and revoked when no longer needed.

Establish verification procedures for sensitive requests. Payment changes, vendor bank detail updates, and executive requests for urgent transfers should require verification through a second, trusted communication channel. Voice or email alone is not sufficient proof of identity.

Train employees on identity risks, not only phishing. Awareness training should cover MFA fatigue, consent phishing, and the importance of reporting unexpected authentication prompts. Employees should understand that approving an MFA request they did not initiate is a security event, not a minor inconvenience.

The Role of Zero Trust in Identity Security

Zero trust is an approach that removes implicit trust based on network location or a previous login. It verifies users, devices, and access requests continuously, and it applies least privilege to every request.

In identity security, zero-trust principles translate into practices such as context-aware access decisions, device posture checks, session monitoring, and re-authentication for sensitive actions. Zero trust is not a single product or a one-time implementation. It is an ongoing approach that assumes an attacker may already have valid credentials and designs controls to limit what those credentials can do.

This assumption is increasingly realistic. If stolen credentials are involved in a substantial share of breaches, security controls must function under the premise that a password may already be compromised. Zero trust does not guarantee security, but it reduces the impact of identity compromise by limiting lateral movement and requiring continuous verification.

Building Identity Security Into Application Development and Testing

Identity controls are not only an IT operations concern. Authentication, authorisation, session handling, and third-party integrations are implemented in software, and weaknesses in those implementations can create identity risks that configuration alone cannot fix.

Evalogical's capabilities align with this need. The company provides application and API testing, integration testing, and quality and reliability validation for business applications and AI-powered workflows. Its secure software development practices and QA capabilities are supported by ISO 9001 and ISO 27001 certified quality management, data privacy, and security processes. For organisations building or integrating applications that handle authentication, role-based access, and third-party OAuth connections, validating those workflows during development-rather than only after deployment-is a practical way to reduce access-control weaknesses.

Discuss Your Application Security Requirements

Conclusion

Identity-based cyberattacks exploit the access that businesses depend on every day. A valid credential, a stolen session token, or an over-permissioned OAuth application can give an attacker the same access as an employee-without malware, without a vulnerability exploit, and often without immediate detection.

The defensive response is not to abandon cloud platforms or multi-factor authentication. It is to strengthen the identity layer: phishing-resistant MFA where it matters most, least privilege, session and token monitoring, OAuth permission reviews, verification procedures for sensitive requests, and employee awareness that covers the full range of identity threats.

Identity protection is not a separate security programme. It is part of the broader cybersecurity strategy, and it deserves the same attention as network security, endpoint protection, and incident response.

Frequently Asked Questions

Q: What are identity-based cyberattacks?

A: Identity-based cyberattacks compromise or misuse an employee's credentials, session, authentication factors, or application permissions to access business systems. The attacker logs in rather than breaking in, and operates within the access granted to that identity. Examples include credential theft, business email compromise, MFA fatigue, session hijacking, and OAuth abuse.

Q: How do cybercriminals steal employee credentials?

A: Common methods include phishing, infostealer malware, credential stuffing using passwords leaked in previous breaches, and fake login pages. Verizon's 2025 DBIR found that credential abuse was an initial access vector in 22% of breaches. Credentials are valuable because they provide direct access to business systems and can be resold.

Q: What is the difference between credential theft and account takeover?

A: Credential theft is the acquisition of usernames, passwords, or authentication secrets. Account takeover is the use of those stolen credentials to log in and control the account. Credential theft is the means; account takeover is the outcome. Session hijacking is different again: it steals the token that proves authentication already happened, bypassing the login process entirely.

Q: How does business email compromise work?

A: BEC involves compromising or impersonating a legitimate business email account to manipulate payments or data. Attackers may use a hijacked account to send fraudulent payment instructions, or spoof a trusted sender to redirect an invoice. The Massachusetts workers union case, in which $6.4 million was lost to a spoofed email, is a documented example. Verification through a second channel is a key control.

Q: What is an MFA fatigue attack?

A: MFA fatigue, or push bombing, occurs when an attacker who already has a valid password repeatedly triggers authentication prompts until the employee approves one. A CISA and FBI advisory names push bombing as one of the most common ways attackers bypass MFA. Number matching and phishing-resistant MFA reduce this risk.

Q: Can attackers bypass multi-factor authentication?

A: Yes. MFA is not absolute. Attackers can bypass it through MFA fatigue, adversary-in-the-middle phishing that captures session tokens, or infostealer malware that steals an already-authenticated session. Microsoft reports that phishing-resistant MFA can prevent up to 99% of identity attacks, but the type of MFA and the surrounding controls matter.

Q: What is session hijacking?

A: Session hijacking is the theft and replay of a session token or cookie that keeps a user logged in. The attacker impersonates the already-authenticated user without needing the password or a new MFA prompt. Infostealer malware is a common method of obtaining session tokens from a browser.

Q: How can OAuth permissions create security risks?

A: OAuth grants third-party applications permission to access account data. Consent phishing tricks users into approving malicious applications that request access to email, files, or contacts. Access tokens can persist after a password reset. Consent phishing campaigns affected 900 tenants and 3,000 user accounts in 2025. Organisations should review connected applications and restrict consent permissions.

Q: Why are privileged accounts common targets?

A: Privileged accounts-administrator and service accounts-have elevated access that can provide broad control over systems and data. Compromising one privileged account can give an attacker more access than compromising several standard accounts. Least privilege, privileged access management, and access reviews reduce this risk.

Q: How does zero-trust security protect business identities?

A: Zero trust removes implicit trust based on network location or a previous login. It verifies users, devices, and access requests continuously, applies least privilege, and monitors sessions. It does not guarantee security, but it limits what a compromised identity can do and reduces lateral movement.

Strengthen Your Application Security with Evalogical

Protecting business identities starts with building reliable applications and validating how users, permissions, and integrations interact. At Evalogical Technologies, we help businesses strengthen their digital solutions through secure software development, application testing, API testing, and integration validation.

Looking to improve your application's security and reliability?

Explore how our technology expertise can support your business


Recommends For You

See All

Share your thoughts