{"id":48050,"date":"2023-05-02T06:10:56","date_gmt":"2023-05-02T10:10:56","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=48050"},"modified":"2023-05-09T08:30:48","modified_gmt":"2023-05-09T12:30:48","slug":"purge-your-company-linkedin-page","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/purge-your-company-linkedin-page\/48050\/","title":{"rendered":"Fake accounts on LinkedIn: time for a purge"},"content":{"rendered":"<p>Among social networks, LinkedIn holds a rather unique position. The platform is designed for communication among professionals, which automatically implies contact with new people, almost complete transparency of user information, as well as a fairly high degree of trust in total strangers.<\/p>\n<p>The downside of this is the relative ease of creating plausible fake profiles. For instance, in the fall of 2022, security expert Brian Krebs <a href=\"https:\/\/krebsonsecurity.com\/2022\/09\/fake-ciso-profiles-on-linkedin-target-fortune-500s\/\" target=\"_blank\" rel=\"nofollow noopener\">uncovered<\/a> a whole bunch of fake LinkedIn accounts purporting to belong to the Chief Information Security Officers of various major international companies. Plus <a href=\"https:\/\/krebsonsecurity.com\/2022\/10\/glut-of-fake-linkedin-profiles-pits-hr-against-the-bots\/\" target=\"_blank\" rel=\"nofollow noopener\">several thousand fake accounts<\/a> listing a real business as employer.<\/p>\n<p>The motives of the scammers vary. But one thing they have in common is that they don\u2019t give a hoot for the <em>HR-brand<\/em> or the reputation of the companies where they supposedly work. Given this \u2014 two questions arise: is it possible to get rid of LinkedIn fakes, and how can you protect your company\u2019s brand?<\/p>\n<h2>How LinkedIn fights fake profiles<\/h2>\n<p>The problem of fake profiles on LinkedIn is far from new. Every six months, the social network <a href=\"https:\/\/about.linkedin.com\/transparency\/community-report#fake-accounts\" target=\"_blank\" rel=\"nofollow noopener\">reports<\/a>, among other things, how many fake accounts it has blocked. The exact figures vary from year to year, but we\u2019re talking tens of millions of profiles every reporting period. For example, from early 2019 to mid-2022, the social network blocked almost 140 million fake accounts.<\/p>\n<p>Most fake LinkedIn profiles (95.4% of them in H1 2022) are blocked automatically. More often than not, fakes are weeded out while still at the registration stage: depending on the period, 70\u201390% of blocked accounts get shot down at takeoff. Fake profiles blocked due to a user complaint make up less than one percent. Nor are there many of them in absolute terms: for example, only 190,000 fakes were blocked because after complaints in H1 2022.<\/p>\n<p>LinkedIn doesn\u2019t specify exactly how it identifies suspicious profiles, but it does give a few details about what raises eyebrows. One red flag is excessive sending of messages. Another is a geographical mismatch \u2014 when \u201cLocation\u201d in the profile shows one region, but the account was registered in an entirely different one. In addition, a page can be flagged as suspicious if it has some patterns common with other fakes that have already been detected and blocked.<\/p>\n<p>Late last year, LinkedIn introduced several innovations set up to combat fakes:<\/p>\n<ul>\n<li>The social network now checks profile photos to see if they are AI-generated.<\/li>\n<li>Suspicious messages now carry warnings.<\/li>\n<li>Another new feature is the \u201cAbout this profile\u201d tab. It shows the approximate date of the account\u2019s registration and other information to help users decide whether it\u2019s trustworthy.<\/li>\n<\/ul>\n<div id=\"attachment_47873\" style=\"width: 3010px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2023\/04\/13104108\/purge-your-company-linkedin-page-EN.png\"><img decoding=\"async\" aria-describedby=\"caption-attachment-47873\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2023\/04\/13104108\/purge-your-company-linkedin-page-EN.png\" alt=\"LinkedIn now has an \" about this profile tab width=\"3000\" height=\"2414\" class=\"size-full wp-image-47873\"><\/a><p id=\"caption-attachment-47873\" class=\"wp-caption-text\">To find the \u201cAbout this profile\u201d tab, press More at the top of the user\u2019s page<\/p><\/div>\n<h2>Is it working?<\/h2>\n<p>But are LinkedIn\u2019s measures to fight fake profiles succeeding? To find out, <em>Wired<\/em> magazine undertook <a href=\"https:\/\/www.wired.com\/story\/linkedin-fake-profiles-state-actors-scams\/\" target=\"_blank\" rel=\"nofollow noopener\">a small experiment<\/a>. First, the journalists created two entirely fake profiles populated with AI-generated texts and photos. The next day, LinkedIn asked both users to confirm their identity and ultimately blocked the accounts.<\/p>\n<p>Next, the journalists tried a different approach: they created a full-blown copy of the profile of one of <em>Wired\u2019s<\/em> own editors; with a single difference \u2014 the profile photo was replaced (with another real picture). Also the only contact information they provided was an e-mail address registered with Proton Mail (an encrypted webmail service popular among folks who value anonymity). This fake account existed on LinkedIn for two whole months, receiving and sending messages, making new contacts and promoting <em>Wired<\/em> content, before the journalists themselves deleted it.<\/p>\n<p>What\u2019s the upshot? This experiment suggests that LinkedIn is pretty good at dealing with simple fakes. But anyone who takes a bit of time and care to produce a more convincing forgery, using real information about a real person, could well slip past LinkedIn\u2019s gatekeepers.<\/p>\n<h2>How to purge your company\u2019s LinkedIn page of fakes<\/h2>\n<p>It is possible that someone is already using your company\u2019s name \u2014 and your real colleagues\u2019 information \u2014 for their own nefarious purposes. Therefore, it would be wise to scrub fake profiles from your company\u2019s list of employees. Start by measuring the scale of the problem: simply compare the number of LinkedIn profiles that list your company as their current employer with actual number of employees.<\/p>\n<p>Also, do a geographic assessment: see how many of your employees are listed in certain regions according to LinkedIn, and compare this with the reality. This should help localize the problem, since fake profiles are very likely to indicate a certain region where scammers are looking for victims. Therefore, fake accounts that give your company as their place of work probably won\u2019t be evenly distributed around the world (most likely they\u2019ll be concentrated in one or several regions).<\/p>\n<p>Depending on the outcome of these checks, and also the overall size of your company, the next steps may vary. If there are relatively few fakes and you managed to localize them geographically, it will be easy enough to identify most of them and report them to LinkedIn support.<\/p>\n<p>If the problem is of a larger scale, it would make sense to start the purge from the top down, prioritizing the fake profiles that impersonate top-level employees. The simplest way would be to take a list of senior managers and search for their LinkedIn profiles by name. If duplicates are found, the real page will most likely be distinguishable from a fake by the date of registration. Also pay attention to geographical mismatches, as well as odd profile pictures.<\/p>\n<p>The platform itself can solve the problem at least with top-level fakes by verifying the accounts of public figures and company executives, for example, using the familiar blue-badges. But, unfortunately, LinkedIn <a href=\"https:\/\/www.wired.com\/story\/linkedin-verification-clear\/\" target=\"_blank\" rel=\"nofollow noopener\">announced<\/a> plans to introduce such a method only in April 2023. For starters, verification will be available in test mode only for a few large U.S. companies. When other organizations will be able to confirm that network users are really their employees is unpredictable.<\/p>\n<h2>Dark side of the moon: fake employees of other companies<\/h2>\n<p>There\u2019s another side to the problem: scammers can attack your employees using fake LinkedIn profiles of people who supposedly work for another organization. You don\u2019t have to look far for an example of where this could lead: just last year this kind of attack <a href=\"https:\/\/www.kaspersky.com\/blog\/sky-mavis-crypto-heist\/44981\/\" target=\"_blank\" rel=\"noopener nofollow\">was carried out<\/a> against Sky Mavis, the developer of the play-to-earn game <em>Axie Infinity<\/em>.<\/p>\n<p>The attackers contacted one of the company\u2019s employees via LinkedIn, supposedly with a job offer. Next, they sent the employee an infected PDF with which they were able to gain access to the company\u2019s network and steal the keys used for transaction validation. With these keys, they cleaned out the company\u2019s cryptocurrency accounts. The losses amounted to more than 500 million U.S. dollars, earning this incident the honorary title of one of <a href=\"https:\/\/www.kaspersky.com\/blog\/top-5-cryptocurrency-heists\/45945\/\" target=\"_blank\" rel=\"noopener nofollow\">the largest crypto heists in history<\/a>.<\/p>\n<p>Defending against such attacks may be not easy. But raising your employees\u2019 awareness of information security can certainly make a huge difference. And the best way to do that is through regular cybersecurity training. The ideal solution for this is the <a href=\"https:\/\/k-asap.com\/en\/?icid=gl_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder____kasap___\" target=\"_blank\" rel=\"noopener\">Kaspersky Automated Security Awareness Platform<\/a>.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kasap\">\n","protected":false},"excerpt":{"rendered":"<p>Why you should purge your company\u2019s LinkedIn page from fake employee profiles, and how to do it.<\/p>\n","protected":false},"author":2726,"featured_media":47874,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3051,3052,2683],"tags":[1977,172,726,4247],"class_list":{"0":"post-48050","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":"category-threats","11":"tag-fake","12":"tag-linkedin","13":"tag-scam","14":"tag-social-networks"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/purge-your-company-linkedin-page\/48050\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/purge-your-company-linkedin-page\/25602\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/purge-your-company-linkedin-page\/21021\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/purge-your-company-linkedin-page\/10538\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/purge-your-company-linkedin-page\/28232\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/purge-your-company-linkedin-page\/25901\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/purge-your-company-linkedin-page\/26294\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/purge-your-company-linkedin-page\/28799\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/purge-your-company-linkedin-page\/35083\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/purge-your-company-linkedin-page\/26225\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/purge-your-company-linkedin-page\/31909\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/purge-your-company-linkedin-page\/31592\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/linkedin\/","name":"LinkedIn"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/48050","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\/2726"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=48050"}],"version-history":[{"count":5,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/48050\/revisions"}],"predecessor-version":[{"id":48129,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/48050\/revisions\/48129"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/47874"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=48050"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=48050"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=48050"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}