Universal Naming Convention credential coercion is a Windows attack technique that forces a system to authenticate to a UNC path under attacker control, usually by making it resolve a remote share or SMB endpoint. The goal is to capture NTLM credentials, relay them, or trigger unwanted outbound authentication from a privileged process.
What UNC credential coercion does
UNC credential coercion abuses a Windows behaviour, not a software bug in the usual sense. The attacker induces the target to reach a remote UNC path, causing the system to attempt authentication outward and expose credentials or session material that should never have left the endpoint.
The technique matters because the authentication attempt can be triggered by common Windows features, including name resolution, file access, printer paths, or other outbound references. Once the victim machine initiates the connection, the attacker can try to capture, relay, or otherwise abuse the resulting authentication.
Why it is dangerous in Windows environments
Its danger comes from trust in outbound authentication. A privileged process, service, or interactive user can be induced to authenticate to an endpoint the organisation does not control, turning a simple path reference into a credential exposure event. That is especially serious where NTLM is still available, because captured material may be replayable or relayable in follow-on attacks.
UNC coercion is also attractive because it can bypass some expectations about user intent. The user may not knowingly submit a password, yet the operating system may still negotiate authentication as part of normal resource access. That makes the technique useful for initial access, privilege escalation, and lateral movement when defenders do not tightly control outbound SMB behaviour.
For a broader identity-and-secret context, the same exposure patterns appear in Ultimate Guide to NHIs — Static vs Dynamic Secrets and Secrets Management Guide, because long-lived credentials are easier to steal, replay, or relay once an authentication exchange is forced out of band.
How organisations reduce exposure
Exposure starts with understanding where outbound authentication is allowed and which systems can be induced to make it. Teams should inventory where Windows hosts can resolve UNC paths, whether SMB egress is broadly permitted, and whether privileged services can be tricked into contacting attacker-controlled shares.
Mitigations usually combine protocol restraint and credential hardening. Restrict outbound SMB where it is not required, limit NTLM where possible, reduce local administrative reach, and prefer stronger authentication paths that are less useful for relay. Where the environment still depends on shared resources, the goal is to make unintended authentication paths harder to trigger and less valuable if they occur.
Operationally, the most useful preventative work is often secret hygiene and access design. API Key Management Guide reinforces the broader principle that credential scope, rotation, and revocation matter because any exposed credential becomes a liability if it is long-lived or over-scoped.
Detection, response, and post-compromise review
Detection should focus on unexpected outbound authentication, especially from servers, service accounts, or administrative sessions that should not be reaching arbitrary hosts. Indicators include suspicious SMB connections, unusual NTLM challenge-response traffic, and outbound requests to external or newly observed shares.
After suspected exploitation, review whether credentials, service accounts, or elevated sessions were captured or relayed. If the technique succeeded, treat the event as an identity exposure problem as much as a network one: rotate any exposed secrets, invalidate affected sessions where possible, and check for follow-on use of the same authentication material elsewhere.
That response model aligns with Guide to the Secret Sprawl Challenge and NHI Authentication Guide, because exposed credentials, weak secret lifecycle controls, and reusable authentication material are what turn one coerced login into a wider compromise.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK and OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1187 — Forced Authentication | Covers coerced outbound auth used to capture or relay credentials. |
| Recommendation — Map coerced outbound logons to T1187 and monitor for unexpected authentication to untrusted hosts. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Applies because coerced auth exposes reusable authenticators and session material. |
| AC-4 — Information Flow Enforcement | Applies because blocking outbound SMB and share access constrains the attack path. | |
| Recommendation — Rotate and revoke exposed authenticators under IA-5 after any suspected coerced authentication. Enforce AC-4 restrictions to prevent systems from reaching attacker-controlled UNC endpoints. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Applies because the technique leverages excessive access and reusable credentials. |
| Recommendation — Apply CIS-6 to reduce standing privilege and constrain accounts that can be coerced. | ||
| OWASP Non-Human Identity Top 10 | NHI-04 — Insecure Authentication | Relevant because forced SMB/NTLM authentication can be abused when auth is weak or relayable. |
| Recommendation — Treat coerced authentication as insecure auth exposure and harden or replace weak protocol paths. | ||
Practitioner Guidance
Why practitioners should care: UNC credential coercion is less about a single exploit and more about an unwanted trust decision made by the operating system. If an attacker can make a system authenticate to them, they may gain material needed for relay, impersonation, or lateral movement without ever asking the user for a password.
What to watch for: Pay attention to systems that routinely make outbound UNC or SMB calls, especially when they hold elevated privileges or run unattended. If those systems also rely on reusable credentials or broad network reach, the coercion path becomes far more useful to an attacker.
Common misunderstanding: The risk is not limited to classic “credential theft” in the phishing sense. The real issue is that Windows may authenticate automatically as part of normal behaviour, so the organisation has to control both the path being requested and the authority behind the authentication.
For a practical control lens, Cloud IAM Role Design Standard Template and RBAC Role Matrix Template support the broader principle of minimising standing privilege, which limits the damage when an authentication exchange is abused.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
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.
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