{"id":37467,"date":"2020-10-27T16:05:25","date_gmt":"2020-10-27T20:05:25","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=37467"},"modified":"2020-10-27T16:05:25","modified_gmt":"2020-10-27T20:05:25","slug":"phishing-via-esp","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/phishing-via-esp\/37467\/","title":{"rendered":"Phishing through e-mail marketing services"},"content":{"rendered":"<p>Scammers have used <a href=\"https:\/\/www.kaspersky.com\/blog\/delayed-phishing-countermeasures\/37153\/\" target=\"_blank\" rel=\"noopener nofollow\">various tricks over the years<\/a> to bypass antiphishing technologies. Another scheme with a high success rate for delivering phishing links to targets is to use e-mail marketing services, also known as e-mail service providers (ESPs) \u2014 companies that specialize in delivering e-mail newsletters \u2014 to send messages. According to statistics we\u2019ve obtained from our solutions, the method is gaining momentum.<\/p>\n<h2>Why ESP-based phishing works<\/h2>\n<p>Companies that are serious about e-mail threats thoroughly scan all e-mail \u2014 with antivirus, antiphishing, and antispam engines \u2014 before letting messages reach users\u2019 inboxes. The engines not only scan message content, headers, and links, but also check the reputation of the sender and any linked websites. Risk verdicts are based on a combination of those factors. For example, if a mass mailing comes from an unknown sender, it looks suspicious, sending up a red flag for security algorithms.<\/p>\n<p>Attackers have found a workaround, however: sending e-mails in the name of a trusted entity. E-mail marketing services, which provide end-to-end newsletter management, fill that role perfectly. They are known; many security solution vendors allow their IP addresses are by default by; and some even skip checks on letters sent through them.<\/p>\n<h2>How ESPs are exploited<\/h2>\n<p>The main attack vector is obvious: It\u2019s phishing disguised as a legitimate mailing. Essentially, cybercriminals become clients of the target service, usually by purchasing the minimum subscription (anything more wouldn\u2019t make much sense, especially given that they can expect to be identified and blocked quickly).<\/p>\n<p>But there exists a more exotic option: using the ESP as a URL host. Under this scheme, the newsletter is sent out through the attackers\u2019 own infrastructure. For example, the cybercriminals can create a test campaign that contains a phishing URL, and send it to themselves as a preview. The ESP creates a proxy for that URL, and then the cybercriminals simply take the proxy URL for their phishing newsletter. Another option for scammers is to create a phishing site that appears to be a mailing template, and provide a direct link to it. But that happens less frequently.<\/p>\n<p>Either way, the new proxy URL now has a positive reputation, so it won\u2019t be blocked; and the ESP, which doesn\u2019t handle the mailing, sees nothing wrong and doesn\u2019t block its \u201cclient\u201d \u2014 at least, not until they start to receive complaints. Sometimes such schemes even play a role in spear-phishing.<\/p>\n<h2>What do ESPs think?<\/h2>\n<p>Unsurprisingly, ESPs are not jumping for joy about being tools for cybercriminals.\u00a0 Most of them have their own security technologies that scan the message content and links that pass through their servers, and almost all provide guidance for anyone encountering phishing through their website.<\/p>\n<p>Therefore, attackers try to keep ESPs calm, too. For example, using a provider for proxies tends to <a href=\"https:\/\/www.kaspersky.com\/blog\/delayed-phishing-countermeasures\/37153\/\" target=\"_blank\" rel=\"noopener nofollow\">delay<\/a> phishing links, so at the time of creation, \u00a0links in test messages appear legitimate; only later do they become malicious.<\/p>\n<h2>What to do<\/h2>\n<p>In many cases, mass mailings are sent to company employees whose addresses are public \u2014 and even the most vigilant among us miss the occasional suspicious or malicious e-mail and click on something we shouldn\u2019t. To protect employees against potential phishing attacks coming from an e-mail marketing service, we recommend the following:<\/p>\n<ul>\n<li>Instruct staff never to open e-mails marked \u201cmass mailing\u201d unless they subscribed to the specific mailing list in question. Such messages are unlikely to be of urgent importance \u2014 they\u2019re usually intrusive advertising at best.<\/li>\n<li>Use robust security solutions that thoroughly scan all incoming e-mail using heuristic algorithms.<\/li>\n<\/ul>\n<p>Among our solutions are <a href=\"https:\/\/www.kaspersky.com\/small-to-medium-business-security\/microsoft-office-365-security?icid=gl_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder____kso365___\" target=\"_blank\" rel=\"noopener nofollow\">Kaspersky Security for Microsoft Office 365 <\/a> and Kaspersky Security for Mail Server, which is a part of <a href=\"https:\/\/www.kaspersky.com\/small-to-medium-business-security?icid=gl_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder_______\" target=\"_blank\" rel=\"noopener nofollow\">Kaspersky Total Security for Business <\/a>. They reliably protect users against this threat.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kesb-trial\">\n","protected":false},"excerpt":{"rendered":"<p>To bypass antiphishing technologies, malefactors can use legitimate e-mail service providers, or ESPs \u2014 but dangerous letters aren\u2019t unstoppable.<\/p>\n","protected":false},"author":2598,"featured_media":37468,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3051,3052],"tags":[19,76,240],"class_list":{"0":"post-37467","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-enterprise","9":"category-smb","10":"tag-email","11":"tag-phishing","12":"tag-spam"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/phishing-via-esp\/37467\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/phishing-via-esp\/22048\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/phishing-via-esp\/17526\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/phishing-via-esp\/23548\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/phishing-via-esp\/21707\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/phishing-via-esp\/20400\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/phishing-via-esp\/24146\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/phishing-via-esp\/23170\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/phishing-via-esp\/29348\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/phishing-via-esp\/8994\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/phishing-via-esp\/15876\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/phishing-via-esp\/16315\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/phishing-via-esp\/14115\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/phishing-via-esp\/25636\/"},{"hreflang":"zh","url":"https:\/\/www.kaspersky.com.cn\/blog\/phishing-via-esp\/12150\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/phishing-via-esp\/26285\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/phishing-via-esp\/23034\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/phishing-via-esp\/28356\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/phishing-via-esp\/28178\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/phishing\/","name":"phishing"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/37467","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2598"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=37467"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/37467\/revisions"}],"predecessor-version":[{"id":37584,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/37467\/revisions\/37584"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/37468"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=37467"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=37467"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=37467"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}