{"id":1242,"date":"2024-06-10T08:54:01","date_gmt":"2024-06-10T15:54:01","guid":{"rendered":"https:\/\/blogs.pugetsound.edu\/infosec\/?p=1242"},"modified":"2024-06-10T08:54:25","modified_gmt":"2024-06-10T15:54:25","slug":"phishing-from-6-7-2024-account-deactivation-request","status":"publish","type":"post","link":"https:\/\/blogs.pugetsound.edu\/infosec\/the-phish-tank\/1242","title":{"rendered":"Phishing from 6\/7\/2024: &#8220;Account Deactivation Request&#8221;"},"content":{"rendered":"\n<p class=\"has-large-font-size\">Original Phishing Message<\/p>\n\n\n\n<p><strong>From:<\/strong> info[@]securityreport[.]gr<br><strong>Subject: <\/strong>Account Deactivation Request For [<em>username<\/em>]@pugetsound.edu<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"457\" src=\"https:\/\/blogs.pugetsound.edu\/infosec\/files\/2024\/06\/6-7-24-IT-account-deactivation-phish-1024x457.png\" alt=\"\" class=\"wp-image-1245\" srcset=\"https:\/\/blogs.pugetsound.edu\/infosec\/files\/2024\/06\/6-7-24-IT-account-deactivation-phish-1024x457.png 1024w, https:\/\/blogs.pugetsound.edu\/infosec\/files\/2024\/06\/6-7-24-IT-account-deactivation-phish-300x134.png 300w, https:\/\/blogs.pugetsound.edu\/infosec\/files\/2024\/06\/6-7-24-IT-account-deactivation-phish-768x342.png 768w, https:\/\/blogs.pugetsound.edu\/infosec\/files\/2024\/06\/6-7-24-IT-account-deactivation-phish-1440x642.png 1440w, https:\/\/blogs.pugetsound.edu\/infosec\/files\/2024\/06\/6-7-24-IT-account-deactivation-phish.png 1496w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"has-large-font-size\">Tips for Detection<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Legitimate emails from Technology Services about your account will come from an @pugetsound.edu email address.<\/li><li>Notice the false sense of urgency regarding the account deactivation timeline. Scammers employ techniques to trick you into acting quickly without thinking. <\/li><li>Always investigate links before clicking. If the link does not go a site you normally log in to related to the account in question, that should be suspicious. <\/li><\/ul>\n\n\n\n<p class=\"has-large-font-size\">Text of Phishing Message<\/p>\n\n\n\n<p><strong>From:<\/strong> info[@]securityreport[.]gr <br><strong>Subject: <\/strong>Account Deactivation Request For [<em>username<\/em>]@pugetsound.edu <\/p>\n\n\n\n<p>Pro postmaster<\/p>\n\n\n\n<p>We have receive a deactivation request from pugetsound.edu on Friday, June 7, 2024 9:30 a.m. and will begin the process shortly.<\/p>\n\n\n\n<p>If this request was not initiated by you, you are strongly advised to cancel this request immediately. Please login again to authenticate this.<\/p>\n\n\n\n<p>CANCEL REQUEST<\/p>\n\n\n\n<p>However, if you do not cancel this request, your email <em>[username]<\/em>@pugetsound.edu will be permanently deleted from pugetsound.edu server.<\/p>\n\n\n\n<p>\u00a92024 Email support &#8211; pugetsound.edu<br>This email was scanned by avast[.]com<br>This is an auto-generated message and replies sent to this address wont be monitored.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Original Phishing Message From: info[@]securityreport[.]grSubject: Account Deactivation Request For [username]@pugetsound.edu Tips for Detection Legitimate emails from Technology Services about your account will come from an @pugetsound.edu email address. Notice the false sense of urgency regarding the account deactivation timeline. Scammers employ techniques to trick you into acting quickly without thinking. Always investigate links before clicking. [&hellip;]<\/p>\n","protected":false},"author":521,"featured_media":1245,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[3],"class_list":["post-1242","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-the-phish-tank","tag-phishing"],"_links":{"self":[{"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/posts\/1242","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/users\/521"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/comments?post=1242"}],"version-history":[{"count":1,"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/posts\/1242\/revisions"}],"predecessor-version":[{"id":1246,"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/posts\/1242\/revisions\/1246"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/media\/1245"}],"wp:attachment":[{"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/media?parent=1242"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/categories?post=1242"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.pugetsound.edu\/infosec\/wp-json\/wp\/v2\/tags?post=1242"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}