{"id":10434,"date":"2026-02-06T04:03:36","date_gmt":"2026-02-06T04:03:36","guid":{"rendered":"https:\/\/serisec.com\/index.php\/2026\/02\/06\/32686\/"},"modified":"2026-02-06T04:03:36","modified_gmt":"2026-02-06T04:03:36","slug":"32686","status":"publish","type":"post","link":"https:\/\/serisec.com\/index.php\/2026\/02\/06\/32686\/","title":{"rendered":"Broken Phishing URLs, (Thu, Feb 5th)"},"content":{"rendered":"<p>    Broken Phishing URLs, (Thu, Feb 5th)<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n    <!-- no image --><br \/>\n \t<BR><br \/>\n<BR><\/BR><\/p>\n<div>\n<p>For a few days, many phishing emails that landed into my mailbox contain strange URLs. They are classic emails asking you to open a document, verify your pending emails, \u2026<\/p>\n<p><img data-recalc-dims=\"1\" decoding=\"async\" alt=\"\" src=\"https:\/\/i0.wp.com\/isc.sans.edu\/diaryimages\/images\/isc-20260205-1.png?ssl=1\" style=\"width: 600px; height: 296px;\"><\/p>\n<p>But the format of the URLs is broken! In a URL, parameters are extra pieces of information added after a question mark (?) to tell a website more details about a request; they are written as name=value pairs (for example \u201cemail=user@domain\u201d), and multiple parameters are separated by an ampersand (&amp;).<\/p>\n<p>Here are some examples of detected URLs:<\/p>\n<pre style=\"background: rgb(238, 238, 238); border: 1px solid rgb(204, 204, 204); padding: 5px 10px;\">\nhxxps:\/\/cooha0720[.]7407cyan[.]workers[.]dev\/?dC=handlers@isc[.]sans[.]edu<span style=\"background-color:#f1c40f;\">&amp;*(Df<\/span>\nhxxps:\/\/calcec7[.]61minimal[.]workers[.]dev\/?wia=handlers@isc[.]sans[.]edu<span style=\"background-color:#f1c40f;\">&amp;*(chgd<\/span>\nhxxps:\/\/couraol-02717[.]netlify[.]app\/?dP=handlers@isc[.]sans[.]edu<span style=\"background-color:#f1c40f;\">&amp;*(TemP<\/span>\nhxxps:\/\/shiny-lab-a6ef[.]tcvtxt[.]workers.dev\/?kpv=handlers@isc[.]sans[.]edu<span style=\"background-color:#f1c40f;\">&amp;*(lIi<\/span><\/pre>\n<p>You can see that the parameters are broken\u2026 \u201c&amp;*(Df\u201d is invalid! It\u2019s not an issue for browsers that will just ignore these malformed parameters, so the malicious website will be visited.<\/p>\n<p>I did not see this for a while but it seems that the technique is back on stage. Threat actors implement this to break security controls. Many of them assume a \u201ckey=value&#8221; format. It may also break regex-based detectionn, URL normalization routines or IOC extraction pipelines\u2026<\/p>\n<p>Of course, we can track such URLs using a regex to extract the last param:<\/p>\n<p><img data-recalc-dims=\"1\" decoding=\"async\" alt=\"\" src=\"https:\/\/i0.wp.com\/isc.sans.edu\/diaryimages\/images\/isc-20260205-2.png?ssl=1\" style=\"width: 700px; height: 144px;\">\u200b\u200b\u200b\u200b\u200b\u200b\u200b<\/p>\n<p>Xavier Mertens (@xme)<br \/>\nXameco<br \/>\nSenior ISC Handler &#8211; Freelance Cyber Security Consultant<br \/>\n<a href=\"https:\/\/keybase.io\/xme\/key.asc\">PGP Key<\/a><\/p>\n<p> (c) SANS Internet Storm Center. https:\/\/isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.<\/p><\/div>\n<p> \t<BR><br \/>\n <BR><\/BR><\/p>\n<p> \t<BR><br \/>\n<BR><\/BR><br \/>\n<a href=\"https:\/\/isc.sans.edu\/diary\/rss\/32686\">Go to isc.sans.edu<\/a><br \/>\n \t<BR><br \/>\n <BR><\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Broken Phishing URLs, (Thu, Feb 5th) For a few days, many phishing emails that landed into my mailbox contain strange URLs. They are classic emails asking you to open a document, verify your pending emails, \u2026 But the format of the URLs is broken! In a URL, parameters are extra pieces of information added after [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[56],"tags":[69],"class_list":["post-10434","post","type-post","status-publish","format-standard","hentry","category-isc-sans-edu","tag-isc-sans-edu"],"_links":{"self":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/10434"}],"collection":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/comments?post=10434"}],"version-history":[{"count":0,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/10434\/revisions"}],"wp:attachment":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/media?parent=10434"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/categories?post=10434"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/tags?post=10434"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}