The Mystery of a Session Cookie
Last Updated: 2015-03-09 21:56:59 UTC
by Lenny Zeltser (Version: 1)
An ISC reader sent us a note about a session cookie that has been appearing in web server logs; the cookie contents triggered cross-site scripting alerts from the Web Application Firewall. Across the various HTTP session instances, the cookie contained the same hash: 3e1dd89fdfa706ed2e69a8eccf98cab048d7b661. Other contents of the cookie included references to malicious-looking third-party URLs that contained affiliate IDs.
I came across an HTTP request on my own server from about a month ago, which contained the same hash value. It looked like this:
References to zeltser.com are normal and non-malicious (that's my server); the mention of "swf-from-pdf-using-swf-mastah" is also normal, because that's the web page that received the malicious request. However, notice the inclusion of an unexpected hostname interyield.jmp9.com and a mention of "adultsearch".
I came across many mentions of the cookie hash value seen above when searching the web, including the following trigger of a SQL injection WAP alert:
I noticed the mention of the cookie value 3e1dd89fdfa706ed2e69a8eccf98cab048d7b661 dating back to 2012.
We're probably dealing with some malicious scanning tool that has this value hardcoded into its cookie-generating code, which is designed to exploit XSS and/or SQL injection vulnerabilities with the goal of redirecting victimized sites' visitors to malicious destinations.
Do you have additional information about this cookie value or would like to share your analysis of this data? Please share your perspective in the discussion forum.
-- Lenny Zeltser
Lenny Zeltser focuses on safeguarding customers' IT operations at NCR Corp. He also teaches how to analyze malware at SANS Institute. Lenny is active on Twitter and Google+. He also writes a security blog.
Looks like someones browser got hijacked...
Mar 10th 2015
8 years ago
Their Perma/ Zombie was picked up as soon as you went into the site would inject on both PC and mobile devices.
Just a thought..
According to Verizon, the header value is a salted hash, and the hash changes on an undisclosed frequency. However, it's easy for third-party ad networks to create a continuous profile by associating old and new X-UIDH values through their own identifier cookie1. Verizon has refused to say what identifier they hash to create the identifier, but their recent patent suggests hashing a phone number. If they are indeed hashing phone numbers, it would be a major cryptographic mistake. Phone numbers can easily be deduced from hashes, so sending those hashes to untrusted web sites is practically equivalent to giving them your phone number.
Here is the latest.
"But even if Verizon now allows subscribers to opt-out of having their online activities tracked using a unique customer code, that option may not satisfy privacy advocates who say consumers are unlikely to understand the implications of default tracking. Some say Verizon should have the feature turned off by default and require people to voluntarily switch it on.
Mar 10th 2015
8 years ago
Nov 26th 2015
7 years ago