In April 2023, global law enforcement scored what appeared to be a decisive victory against the illicit trade in stolen digital identities. Under the banner of "Operation Cookie Monster," the Federal Bureau of Investigation, working alongside the U.S. Department of Justice and law enforcement agencies across 17 countries, successfully seized Genesis Market. The invite-only dark web platform had long served as a premier hub for cybercriminals seeking to purchase access to compromised accounts. At the time of its takedown, authorities discovered a staggering repository of data: 80 million stolen credentials harvested from approximately 1.5 million infected devices worldwide.
What made Genesis Market particularly dangerous was not just its catalog of compromised usernames and passwords, but its supply of hijacked session cookies. These digital tokens allowed scammers to bypass traditional login procedures entirely, granting them instant access to target accounts without ever needing to input a password or pass a multi-factor authentication prompt.
Yet, despite the dismantlement of Genesis Market, the underlying threat ecosystem has proven resilient. Bundles of leaked session tokens—collectively known as "stealer logs"—continue to be harvested on a massive scale and traded across alternative dark web marketplaces and private messaging platforms. Research published by NordVPN underscores the staggering magnitude of the issue, with analysts counting more than 52.4 billion stolen cookies within infostealer datasets logged between June 2025 and June 2026.
While the sheer volume of compromised data paints a grim picture of modern cybersecurity, experts note that session hijacking is not an unresolvable threat. Because stolen session cookies rely on active authorization states, revoking active sessions within a service’s security settings invalidates the hijacked tokens instantly. Achieving safety, however, requires understanding how browser sessions are weaponized, where stolen data is traded, how individuals can detect potential leaks, and how emerging web standards aim to mitigate the risk altogether.
What makes browser sessions so valuable?
To understand why cybercriminals prioritize session cookies over conventional passwords, it is necessary to examine how modern web authentication operates. Whenever a user successfully logs into an online service, the destination server generates a small text file—a session cookie—and transmits it to the user’s web browser. Embedded within this file is a unique session identification code that acts as a digital passkey.
For as long as the user remains active, the web application reads this session ID with every page request or interaction. This architecture spares the user from having to re-enter their login credentials every time they navigate to a new page, refresh a tab, or submit a request on the platform.
To maintain usability, session cookies are configured with expiration windows that can range from a few brief hours to several consecutive weeks. When the expiration threshold is reached, the server invalidates the session ID, logging the user out and prompting them to authenticate once again. However, if a malicious actor acquires a copy of a valid session cookie before it expires, the underlying security model breaks down. By importing the stolen cookie into their own browser, an attacker can piggyback on the active session, impersonating the victim without ever triggering standard credential checks.
To harvest these assets, cybercriminals rely heavily on specialized malware known as infostealers. Prominent infostealer strains operating across the threat landscape include Lumma, Vidar, StealC, Acreed, and Atomic Stealer (also known as AMOS). These malicious programs spread through several common vectors, including compromised or malvertising-laden websites, pirated software downloads, and trojanized software installers disguised as legitimate utility applications.
Once an infostealer successfully executes on a target device, it quietly monitors system activities and extracts sensitive data stored within local browsers and applications. The malware harvests stored passwords, personal identification numbers (PINs), autofill form details, and active session cookies. All of this gathered information is aggregated into a single file known as a stealer log, which is then exfiltrated directly back to the attack operator.
Armed with a fresh stealer log, an attacker can choose between exploiting the data directly or listing it for sale on cybercrime marketplaces. If an attacker imports these logs into their browser environment, they gain immediate operational control over the victim’s logged-in web accounts. In many cases, threat actors utilize this window of access to alter account settings, reset passwords, log out legitimate device sessions, and permanently lockout the original owner.
How stealer logs get sold on the dark web
Following the seizure of Genesis Market, the cybercriminal supply chain adapted rapidly, establishing alternative channels to distribute stealer logs. Russian Market has largely emerged as the primary web-based successor storefront for black-hat cybercriminals seeking illicit credential bundles, even as a massive portion of the market has migrated to private communication channels.
According to threat intelligence analysts at DarkOwl, Russian Market processed approximately 180,000 stealer log transactions during the first half of 2025 alone. A key factor driving the platform’s adoption is its user-friendly, open-web accessibility. Unlike traditional dark web marketplaces that require specialized routing networks like the Tor browser or specific .onion address links, Russian Market maintains accessible storefront infrastructure. This accessibility lowers the barrier to entry, enabling virtually any malicious actor to purchase bulk stealer logs and attempt account takeovers at scale.
However, web-based storefronts represent only a fraction of the current trade. Research conducted by Flare Research indicates that market figures from traditional platforms drastically understate the true scope of the threat, estimating that roughly 90% of all stolen session logs are now traded privately within the Telegram messaging app.
On Telegram, cybercriminals leverage automated sales chatbots that replicate standard e-commerce experiences. Buyers can interact with storefront bots to browse available stealer logs using customizable search filters, sorting inventory by country of origin, target software application, and account privilege levels (such as administrative or corporate access). Depending on the perceived value of the compromised accounts contained within a log, prices typically range from as little as $5 to upwards of $500 per log bundle.
How to check if your session cookies have leaked
Determining whether an individual’s session cookies have been compromised poses a significant challenge due to the decentralized nature of the threat landscape. There is no comprehensive, universal database that aggregates every stolen cookie or infostealer log traded across underground markets. While enterprise organizations often deploy specialized threat intelligence subscriptions costing hundreds or thousands of dollars per month to monitor dark web markets for corporate telemetry, such solutions are largely impractical for everyday consumers.
Nevertheless, consumer-accessible methods exist to detect potential session hijacking. The most direct approach involves auditing active login sessions directly through the security settings of frequently used online services. Most major platforms provide a security dashboard displaying all currently authenticated devices, along with associated IP addresses, device types, and geographic locations.
If an unfamiliar device or unexpected geographical location appears on the active session list, it strongly indicates that an unauthorized party has accessed the account. Security experts note, however, that location tracking can occasionally yield false positives or imprecise readings if the account owner uses privacy tools such as a Virtual Private Network (VPN) or Apple’s iCloud Private Relay. As a defensive measure, periodically executing a manual "log out of all active sessions" command forces the server to terminate all existing tokens, requiring a fresh login that effectively invalidates unauthorized persistent sessions.
Additionally, public breach notification services offer a secondary line of detection. Platforms such as Have I Been Pwned monitor known data dumps, dark web forums, and criminal marketplaces for exposed credentials. Although Have I Been Pwned does not specifically track raw session cookies, an email address or password appearing in a breach dataset serves as a strong indicator that associated session cookies were likely captured during the same infostealer infection. Users can register their email addresses with the service to receive automated alerts whenever their details surface in newly uncovered breaches.
For users seeking dedicated monitoring tools, select consumer cybersecurity suites have begun integrating specialized session-tracking capabilities. For example, NordVPN offers hijacked session monitoring features within its Complete and Prime service tiers, actively scanning dark web sources for session leaks that could directly impact subscriber accounts.
What to do if your sessions are compromised
When confirmation arises that session cookies have been stolen and an account takeover attempt is underway, taking prompt remedial action is critical. However, security professionals emphasize that the precise order of operations during remediation is vital to successfully recovering compromised accounts. Performing remediation steps in an incorrect sequence can allow attackers to intercept new credentials or immediately re-establish access before the underlying infection is addressed.
The initial priority must always focus on securing the local device environment. Because stealer logs are generated by active infostealer malware residing on the infected system, changing passwords prior to clearing the malware simply results in the new credentials being harvested once again. Consequently, users must first isolate the affected device and run a comprehensive antivirus or anti-malware scan using up-to-date threat definitions to identify and eradicate any hidden infostealers, trojans, or malicious browser extensions.
Once the host system is confirmed clean, the next step involves immediately invalidating all active session tokens associated with compromised accounts. Users should access their account management dashboards from a secure, clean device and select the option to terminate all active sessions across all devices. This step cuts off any unauthorized access currently maintained by attackers using stolen cookies.
Only after active sessions have been revoked should users proceed to update their account passwords. New passwords should be strong, unique, and generated independently for every account to prevent credential-stuffing attacks across multiple platforms. Finally, users should re-verify or enable multi-factor authentication (MFA)—preferably utilizing authenticator applications or hardware keys rather than SMS-based codes—and review security settings to ensure that unauthorized recovery email addresses or secondary access methods were not added by the intruder during the breach.
Reducing security risk from session cookies
While traditional session management remains vulnerable to local malware exfiltration, structural shifts in web architecture are underway to address the problem at the protocol level. A primary effort in this space is the Device Bound Session Credentials (DBSC) initiative, an open-web standard being developed in alignment with the World Wide Web Consortium (W3C).
DBSC aims to fundamentally alter how browser sessions are authenticated by cryptographically linking each online session to a specific hardware device. Under the proposed standard, when a user logs into a web application, the session is tied to a private cryptographic key stored securely within the local host device’s dedicated hardware security chip (such as a Trusted Platform Module, or TPM).
When a request is made to the service, the browser must prove possession of the private key. Because the private key is locked within the physical device’s security hardware and cannot be read or exported by software-level infostealers, an attacker who steals the session cookie alone will be unable to use it from a secondary device, effectively neutralizing cookie-based account takeovers.
Implementation of the standard is already moving forward in select environments. Google has deployed native support for Device Bound Session Credentials within its Chrome web browser for Windows, integrating the feature to protect native Google services such as Gmail and Google Docs. Chrome users on macOS are also receiving access to the security feature through a gradual rollout.
However, the technology’s overall protective coverage remains limited by current industry adoption. Although the DBSC standard has been open-sourced for broad implementation, no other major third-party online service providers or competing web infrastructure vendors have fully deployed native support for the protocol. As a result, the practical security benefits of DBSC are presently confined primarily to native Google ecosystem applications, Chrome environments on supported desktop operating systems, and third-party websites that utilize Google Single Sign-On (SSO) mechanisms. Cybersecurity analysts suggest that as more web browsers and service operators incorporate the standard, the systemic threat posed by dark web stealer logs could finally begin to diminish.