Forge Web Credentials: Web Cookies
- ID
- T1606.001
- Tactics
- TA0006 Credential Access
- Sub-technique of
- T1606 Forge Web Credentials
- Platforms
- Linux, macOS, Windows, SaaS, IaaS
- Data sources
- Logon Session Creation, Web Credential Usage, File Creation, File Access, Network Connection Creation
- Source
- attack.mitre.org
- MITRE last modified
- 25 Oct 2025
Adversaries may forge web cookies that can be used to gain access to web applications or Internet services. Web applications and services (hosted in cloud SaaS environments or on-premise servers) often use session cookies to authenticate and authorize user access.
Adversaries may generate these cookies in order to gain access to web resources. This differs from Steal Web Session Cookie and other similar behaviors in that the cookies are new and forged by the adversary, rather than stolen or intercepted from legitimate users. Most common web applications have standardized and documented cookie values that can be generated using provided tools or interfaces.[1] The generation of web cookies often requires secret values, such as passwords, Private Keys, or other cryptographic seed values.
Once forged, adversaries may use these web cookies to access resources (Web Session Cookie), which may bypass multi-factor and other authentication protection mechanisms.[2][1][3]
Detection
- DET0171 Detection Strategy for Forged Web Cookies
Data components: Logon Session Creation, Web Credential Usage, File Creation, File Access, Network Connection Creation
Mitigations (2)
- M1047 Audit
Administrators should perform an audit of all access lists and the permissions they have been granted to access web applications and services. This should be done extensively on all resources in order to establish a baseline, followed up on with periodic audits of new or updated resources. Suspicious accounts/credentials should be investigated and removed.
- M1054 Software Configuration
Configure browsers/applications to regularly delete persistent web cookies.