Evercookie

Evercookie (also known as supercookie ) was an open-source JavaScript application programming interface (API) that identifies and reproduces intentionally deleted cookies on the clients' browser storage. This behavior is known as a zombie cookie. It was created by Samy Kamkar in 2010 to demonstrate the possible infiltration from the websites that use respawning. Websites that have adopted this mechanism can identify users even if they attempt to delete the previously stored cookies. In 2013, Edward Snowden leaked a top-secret NSA document that showed Evercookie can track Tor (anonymity networks) users. Many popular companies use functionality similar to Evercookie to collect user information and track users. Further research on fingerprinting and search engines also draws inspiration from Evercookie's ability to track a user persistently. In the late 2010s, most modern browsers have implemented ways to get rid of evercookies with minimal manipulation, notably closing the evercookie tab and then clearing website data in the browser. Evercookie is mostly outdated in 2026, because the software it used, like Java applet or Adobe Flash, have been removed from browsers and storage space like, local storage, session storage, indexed DB, and cookies, can be easily cleaned via browser settings and external plugins like Cookie AutoDelete.

Evercookie (also known as supercookie ) was an open-source JavaScript application programming interface (API) that identifies and reproduces intentionally deleted cookies on the clients' browser storage. This behavior is known as a zombie cookie. It was created by Samy Kamkar in 2010 to demonstrate the possible infiltration from the websites that use respawning. Websites that have adopted this mechanism can identify users even if they attempt to delete the previously stored cookies. In 2013, Edward Snowden leaked a top-secret NSA document that showed Evercookie can track Tor (anonymity networks) users. Many popular companies use functionality similar to Evercookie to collect user information and track users. Further research on fingerprinting and search engines also draws inspiration from Evercookie's ability to track a user persistently. In the late 2010s, most modern browsers have implemented ways to get rid of evercookies with minimal manipulation, notably closing the evercookie tab and then clearing website data in the browser. Evercookie is mostly outdated in 2026, because the software it used, like Java applet or Adobe Flash, have been removed from browsers and storage space like, local storage, session storage, indexed DB, and cookies, can be easily cleaned via browser settings and external plugins like Cookie AutoDelete. ==Background== There are three commonly used data storages, including HTTP cookies, flash cookies, HTML5 Storage, and others. When the user visits a website for the first time, the web server may generate a unique identifier and store it on the user's browser or local space. The website can read and identify the user in its future visits with the stored identifier, and the website can save user's preferences and display marketing advertisements. Due to privacy concerns, all major browsers include mechanisms for deleting and/or refusing cookies from websites. In response to the users' increased unwillingness to accept cookies, many websites employ methods to circumvent users' deletion of cookies. Started from 2009, many research teams found popular websites used flash cookies, ETags, and various other data storage to rebuild the deleted cookies by users, including hulu.com, foxnews.com, spotify.com, etc. In 2010, Samy Kamkar, a Californian programmer, built an Evercookie project to further illustrate the tracking mechanism with respawning across various storage mechanisms on browsers. ==Description== Evercookie allows website authors to be able to identify users even after said users have attempted to delete cookies. Samy Kamkar released v0.4 beta of the evercookie on September 13, 2010, as an open source project. Evercookie is capable of respawning deleted HTTP cookies by storing the cookies on multiple different storage systems typically exposed by web browsers. When a browser visits a website with the Evercookie API on its server, the web server can generate an identifier and store it on various storage mechanisms available on that browser. If the user removes some but not all of the stored identifiers on the browser and revisits the website, the web server retrieves the identifier from storage areas that the user failed to delete. Then the web server will copy and restore this identifier to the previously cleared storage areas. By abusing the various available storage mechanisms, Evercookie creates persistent data identifiers, because users are unlikely to clear all storing mechanisms. From the list provided by Samy Kamkar, 17 storage mechanisms could be used for the v0.4 beta Evercookie when they are available on browsers: Standard HTTP cookies HTTP Strict Transport Security (HSTS) Local shared objects (Flash cookies) Silverlight Isolated Storage Storing cookies encoded in RGB values of auto-generated, force-cached PNG images using HTML5 Canvas tag to read pixels (cookies) back out Storing cookies in Web history Storing cookies in HTTP ETags Storing cookies in Web cache window.name caching Internet Explorer userData storage HTML5 Session Web storage HTML5 Local Web storage HTML5 Global Storage HTML5 Web SQL Database via SQLite HTML5 IndexedDB Java JNLP PersistenceService Java CVE-2013-0422 exploit Samy Kamkar claims that he did not intend to use the Evercookie project to violate internet user privacy or to sell to any parties for commercial use. However, it has served as an inspiration for other commercial websites that later implemented similar mechanisms to restore user-deleted cookies. The Evercookie project is open source, meaning everyone can access and examine the code, or use the code for any purpose. The project incorporates HTML5 as one of the storage mechanisms, which was released 6 months before the project and gained public attentions due to its added persistency. Kamkar wished his project could demonstrate how users' privacy can be infiltrated by contemporary tracking tools. In 2010, one way to prevent Evercookie respawning was a Firefox browser plug-in named "Anonymizer Nevercookie™". The storage mechanisms incorporated in the Evercookie project are constantly being updated, adding to Evercookie's persistency. As it incorporates many existing tracking methods, Evercookie provides an advanced data tracking tool that reduces the redundancy of data collection methods by many commercial websites. An increasing number of commercial websites used the idea of Evercookie, and added upon it by incorporating new storage vectors. In 2014, a research team at the Princeton University conducted a large scale study of three persistent tracking tools: Evercookie, canvas fingerprinting, and cookie syncing. The team crawled and analyzed the top 100,000 Alexa websites, and detected a new storage vector, IndexedDB, that is incorporated into an Evercookie mechanism and used by weibo.com. The team claimed this is the first detection of commercial use for IndexedDB. Moreover, the researchers discovered cookie syncing is used in conjunction with Evercookie. Cookie syncing allows data sharing between different storage mechanisms, facilitating Evercookie's respawning process in different storage locations on users' browsers. The team also discovered instances of Flash cookies respawning HTTP cookies, and HTTP cookies respawning the flash cookies on the commercial websites. Those two mechanisms are different from the Evercookie project in terms of the number of storage mechanisms employed, but they follow the same principle. Among the sites that the research team crawled, 10 out of 200 websites used flash cookies to rebuild HTTP cookies. 9 of the observed sites belonged to China (including sina.com.cn, weibo.com, hao123.com, sohu.com, ifeng.com, youku.com, 56.com, letv.com, and tudo.com). The other website identified was yandex.ru, a top search engine in Russia. ==See also== ==References==

Text derived from https://en.wikipedia.org/w/index.php?oldid=1376313169 under CC BY-SA 4.0; modifications have been made.