TL;DR: 22% of breaches assessed in Verizon’s 2025 DBIR involved compromised credentials, and ThreatLocker says valid logins are a practical attack path. Session handling has to be narrowed after sign-in so one stolen account cannot turn into broader access.
Editorial analysis by NHI Mgmt Group, based on content published by ThreatLocker: “Cybercriminals are increasing credential theft attacks”.
By the numbers:
- 22% of the breaches assessed in Verizon’s 2025 DBIR used compromised credentials as the initial access vector.
- ThreatLocker says stolen credentials are involved in roughly 60% of financial cyberattacks.
- The article says an illicit database contained over 149 million usernames and passwords.
Key questions
Q: Why do stolen credentials create such high risk in cloud identity attacks against SaaS and IdPs?
A: Stolen credentials are dangerous because they often unlock trusted identity paths rather than just a single app.
Q: How can security teams detect credential theft attacks?
A: Security teams detect credential theft attacks by watching for stolen secrets being used from new devices, locations or applications.
Q: What breaks when stolen credentials are replayed as valid logins?
A: What breaks is the assumption that successful authentication equals legitimate use.
Practitioner guidance
- Restrict login to approved devices and locations Require SaaS, cloud and remote-access logins to originate from approved endpoints, networks or brokered access paths so stolen credentials are not usable everywhere.
- Invalidate live sessions after suspected compromise Terminate active cookies, tokens and authenticated sessions when credential theft is suspected so an attacker cannot keep using an already-issued trust state.
- Reduce the scope of each account Enforce least privilege and remove unnecessary local admin rights so a compromised identity cannot reach more systems than it truly needs.
Bottom line: Credential theft now works because attackers can use legitimate authentication paths, not because they need to break encryption or exploit code.
Glossary terms: Credential Theft, Session Token Exposure, Phishing-Resistant MFA, Identity Blast Radius
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Credential theft is now an access-control problem, not only a password problem. Once attackers authenticate successfully, the security question shifts from stopping entry to proving that the session, device and location are still trustworthy. That makes identity telemetry part of containment, not just investigation. Teams that keep treating login as the security boundary are leaving the real decision point ungoverned.
A question worth separating out:
Q: Should organisations prioritise token revocation or password resets after suspected compromise?
A: Token revocation usually comes first when the incident involves OAuth, refresh tokens, API keys, or other delegated access. Password resets help only if the attacker depended on interactive login. When the compromise path includes connected apps, the priority is to cut off every issued credential and consented integration before restoring user access.
👉 Read our full editorial: Credential theft is turning legitimate logins into breach access