Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Cookie theft steals the session cookies that prove a user has already logged in, letting an attacker resume the session on their own machine without a password or a second factor.

What Is Cookie Theft?
Cookie theft is the capture and reuse of the browser cookies that represent an authenticated session. When you sign in to an application, the server issues a cookie that says, in effect, “this browser has already proved who it is”. Anyone holding that cookie can present it and be treated as you, for as long as it remains valid.
That makes session cookies a better prize than passwords. A password can be changed and is usually protected by a second factor; a session cookie represents an authentication that has already completed, so presenting it generates no login prompt and no multi-factor challenge. MITRE ATT&CK covers the theft as T1539 and the reuse as T1550.004.
HttpOnly and send it elsewhere.The hijacking of the Linus Tech Tips YouTube channels in March 2023 is a useful public example: an employee opened a malicious attachment presented as a sponsorship offer, the stealer took session cookies, and the attackers took over the channels without ever knowing a password. The same pattern underlies a large share of Microsoft 365 account compromises, where an attacker imports a stolen cookie, reads mail, creates an inbox rule, and starts invoice fraud.
Browsers encrypt their cookie stores, but historically the key was available to any process running as the same user, which is precisely the position an infostealer is in. Chrome’s App-Bound Encryption, introduced in 2024, ties the key to the browser application so that another process running as the user cannot decrypt the store directly. Stealer developers responded within months with techniques that borrow the browser’s own context. The arms race continues, and relying on it alone is unwise.
For applications you build or operate:
HttpOnly, Secure, and an appropriate SameSite value on every session cookie, and scope the path and domain tightly.For the enterprise estate:
Session security review, including cookie attributes and reauthentication logic, is part of our web application security services.
Yes, and that is why it is so widely used. The cookie is issued after authentication has completed, including any second factor, so replaying it resumes an already-trusted session rather than starting a new login. Defending against it requires session-level controls such as device binding, conditional access, short lifetimes, and continuous access evaluation, not stronger login factors alone.
It stops JavaScript running in the page from reading the cookie through document.cookie, which blocks the cross-site scripting route to theft. It does nothing against malware on the endpoint, which reads the browser’s cookie database directly, and nothing against an adversary-in-the-middle proxy that captures the cookie as the server issues it. Set it regardless; it is free and it closes one path.
Revoke all active sessions and refresh tokens for the account rather than only resetting the password, because a password change does not always invalidate existing sessions. Then review mailbox rules, forwarding settings, OAuth application grants, and recent sign-in locations. If malware is suspected on the device, treat the endpoint as compromised and investigate what else was taken from it.
They solve the phishing of credentials, which removes one common route to a session. They do not change what happens after sign-in: the application still issues a session cookie or token that can be stolen by malware on the device. Pair passkeys with device-bound sessions, short token lifetimes, and conditional access for meaningful protection.
You May Be Interested In These
Cybersecurity Terms
17 November 2026
What Is the Difference Between Fail-Secure and Fail-Safe?
Read More
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.