Watering-Hole Attack
Pronunciation: WAW-ter-ing HOHL uh-TAK
Definition
Watering-Hole Attack is a targeted compromise in which attackers infect or imitate a website or online resource frequently used by the intended victim group and wait for members to visit. Attackers choose a site or resource commonly visited by their intended victims, compromise it or imitate it, and use that trusted context to deliver malicious content or credential capture.
Overview
Meaning and boundaries
Watering-Hole Attack is a targeted compromise in which attackers infect or imitate a website or online resource frequently used by the intended victim group and wait for members to visit. Attackers choose a site or resource commonly visited by their intended victims, compromise it or imitate it, and use that trusted context to deliver malicious content or credential capture. For payment teams this might affect a developer forum, vendor portal, wallet download page, or industry resource used during routine work.
How it works in practice
The attacker targets a trusted location shared by victims rather than contacting each person directly. Compromised sites, advertisements, scripts, downloads, browser exploits, or authentication prompts can deliver malware, steal credentials, or collect intelligence about selected organizations. Organizations should patch browsers and endpoints, isolate high-risk browsing, filter malicious content, monitor trusted sites and DNS, use application controls, protect credentials, and analyze unusual web behavior. Retain visited domain and URL, DNS and certificate data, page or script artifacts, endpoint events, exploit chain, affected users, credentials, infrastructure indicators, and containment. Assessment of Watering-Hole Attack should trace a targeted compromise in which attackers infect or imitate a website or online resource frequently used by the intended victim group and wait for members to visit from prerequisite and entry point through observable impact on the affected service.
Checks and failure points
Reduce exposure through patching, browser isolation where appropriate, endpoint controls, verified software sources, and prompt investigation of unexpected downloads or authentication prompts. Reputation of a familiar site is not sufficient evidence that its current content is safe.
How it differs from related terms
Unlike broad phishing that sends bait directly to victims, a watering-hole attack waits at a location the target group is likely to visit. Related entries: Spear Phishing.
Example
A finance team follows a link to a frequently used partner portal that has been compromised. A counterfeit sign-in prompt attempts to steal its treasury credentials.
Comparison
Unlike broad phishing that sends bait directly to victims, a watering-hole attack waits at a location the target group is likely to visit.
Key Takeaway
Treat familiar third-party websites as potentially compromised dependencies.
Sources
- Avoiding Social Engineering and Phishing Attacks — CISA (2026-08-03)
- Digital Identity Guidelines, SP 800-63-4 — NIST (2026-08-03)
- MITRE ATT&CK: Drive-by Compromise — MITRE (2026-08-03)