Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› Credential Watering Hole
Threats, Abuse & Incident Response

Credential Watering Hole

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Threats, Abuse & Incident Response

A credential watering hole is a credential theft technique that targets a place where users repeatedly authenticate, such as a login page, portal or SSO flow. The attacker captures usernames, passwords, session tokens or MFA prompts by compromising that trusted path rather than each person individually.

How Credential Watering Holes Work

A credential watering hole is not about chasing individual users one by one. It exploits a trusted authentication point that many people revisit, then uses that concentration of trust to intercept credentials, session tokens, or MFA prompts at scale.

The key difference from simple phishing is that the attacker compromises the place where authentication already happens, which can make the flow look normal to the user and harder to question. That is why these campaigns often succeed even when the target audience is alert to obvious lures.

Because the technique depends on trust in a familiar login path, defenders should treat login pages, portals, and SSO journeys as security-critical attack surfaces. The same browser session that makes access convenient can also become the point where tokens, cookies, or prompts are exposed if the path is tampered with.

Watering Hole Attacks Guide covers the broader attack pattern, including compromised sites, visitor profiling, detection signals, and hardening for browsers, DNS, and endpoints.

Why Trusted Login Paths Are Attractive Targets

Credential watering holes are effective because they turn legitimate user behaviour into the attack path. If users must authenticate through the same entry point repeatedly, compromise of that point can expose many credentials or sessions without requiring separate lures for each victim.

Attackers value these paths because they can harvest high-value material, including usernames, passwords, session cookies, and MFA interactions, while blending into normal access traffic. In practice, that can give them a way to bypass the front door rather than break it.

This pattern is especially dangerous where the login experience is embedded in a portal, browser workflow, or identity provider path that users trust implicitly. If the attacker can alter page content, inject prompts, or redirect authentication, the compromise may look like an ordinary sign-in failure or retry rather than an active theft event.

MITRE ATT&CK T1189 Drive-by Compromise is a useful lens for understanding how browser-facing compromise can lead to credential theft and session-token abuse.

Where Organisations Should Look for Exposure

Exposure starts with the assets that host or front the authentication journey: web portals, SSO redirects, login subdomains, identity provider integrations, browser extensions, and any third-party components that influence the sign-in flow. If those paths are not inventoried, they are easy to overlook.

Internet exposure matters too. Publicly reachable portals, redirect endpoints, and federated login pages deserve particular scrutiny, because the attacker only needs one compromised trust point to affect many users. Vendor advisories, browser hardening notes, and identity platform notices are all relevant when a login surface changes.

Teams should also review whether the login flow depends on static secrets, long-lived tokens, or weak session handling, because those materials increase the value of interception. A stolen session token can be just as useful as a password when it is accepted by downstream services.

Secrets Management Guide explains why secret lifecycle, rotation, and secretless design matter when authentication material is reused across systems.

OWASP Non-Human Identity Top 10 is also relevant where stolen authentication material belongs to automated or service-based access paths rather than human-only sessions.

How to Contain and Detect the Technique

When a watering hole is suspected, containment should focus on the affected trust path, not only on the user accounts. That usually means disabling the compromised page or redirect, invalidating exposed sessions, and reviewing the authentication broker, reverse proxy, or browser-delivered content that may have been altered.

Detection is strongest when organisations correlate authentication anomalies with web, DNS, and endpoint telemetry. Unusual login page changes, unexpected redirects, unfamiliar prompt behaviour, and bursts of token use after a normal sign-in are all signs that the trusted path may have been abused.

After remediation, review whether any credentials, refresh tokens, cookies, API keys, or linked sessions were captured before the compromise was removed. If the answer is unknown, treat the incident as a potential identity compromise, not just a web-content issue.

RFC 6749: The OAuth 2.0 Authorization Framework helps explain why bearer-style credentials and delegated access material require careful handling when authentication flows are attacked.

API Key Management Guide is a useful follow-on reference when the compromise may have exposed reusable access keys alongside user credentials.

Risk and Threat Considerations

Credential watering holes are risky because they let an attacker concentrate on a single trusted access path and then harvest multiple identities, sessions, or prompts from that one point of compromise. That creates a high-leverage theft path, especially when users repeatedly authenticate through the same portal or SSO flow.

Failure mechanism: The attacker compromises or impersonates the login surface, then captures secrets, tokens, or MFA interactions as users pass through the trusted path.

Impact: A successful watering hole can lead to account takeover, session hijacking, lateral movement through connected applications, and repeated access until the exposed material is revoked.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP Non-Human Identity Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP Non-Human Identity Top 10NHI-02 — Secret LeakageCovers theft of credentials and tokens from trusted auth paths.
NHI-07 — Long-Lived SecretsApplies when intercepted material stays usable too long after capture.
Recommendation — Scan login flows for leaked secrets and revoke exposed credentials immediately. Replace long-lived login secrets with shorter-lived, revocable credentials.
MITRE ATT&CKT1189 — Drive-by CompromiseDescribes compromising a trusted web path to reach users and steal credentials.
Recommendation — Map the compromised login path to T1189 and hunt for follow-on credential theft.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementDirectly addresses lifecycle handling for passwords, tokens, and authenticators.
IA-2 — Identification and Authentication (Organizational Users)Login-path abuse targets the organisation's user authentication control plane.
AU-6 — Audit Record Review, Analysis, and ReportingSupports detection and review of suspicious authentication and session activity.
Recommendation — Enforce IA-5 to manage, rotate, and revoke exposed authenticators and tokens. Strengthen IA-2 by hardening user sign-in and reducing attackable authentication touchpoints. Review authentication logs for unusual sign-in, redirect, and session-use patterns.

Practitioner Guidance

Why practitioners should care: Treat the authentication journey as a protected asset, not just a convenience feature. If the login path is compromised, the control plane for user access can be undermined even when individual accounts remain technically intact.

What to watch for: Pay attention to changes in login-page behaviour, unexpected redirects, prompt fatigue patterns, and post-login session anomalies. Those signals often reveal the attack before downstream systems show obvious abuse.

Practitioner takeaway: The safest response is to inventory every trusted authentication path, harden the path itself, and be ready to revoke sessions and rotate exposed secrets when the path is suspected of compromise.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org