{"id":28374,"date":"2024-12-10T22:14:02","date_gmt":"2024-12-10T16:44:02","guid":{"rendered":"https:\/\/www.kaspersky.co.in\/blog\/nearest-neighbor-wi-fi-attack\/28374\/"},"modified":"2024-12-10T22:14:02","modified_gmt":"2024-12-10T16:44:02","slug":"nearest-neighbor-wi-fi-attack","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.in\/blog\/nearest-neighbor-wi-fi-attack\/28374\/","title":{"rendered":"Nearest Neighbor: a remote attack on Wi-Fi networks"},"content":{"rendered":"<p>From the perspective of information security, wireless networks are typically perceived as something that can be accessed only locally\u00a0\u2014 to connect to them, an attacker needs to be physically close to the access point. This significantly limits their use in attacks on organizations, and so they are perceived as relatively risk-free. It\u2019s easy to think that some random hacker on the internet could never simply connect to a corporate Wi-Fi network. However, the newly emerged Nearest Neighbor attack tactic demonstrates that this perception is not entirely accurate.<\/p>\n<p>Even a well-protected organization\u2019s wireless network can become a convenient entry point for remote attackers if they first compromise another, more vulnerable company located in the same building or a neighboring one. Let\u2019s delve deeper into how this works and how to protect yourself against such attacks.<\/p>\n<h2>A remote attack on an organization\u2019s wireless network<\/h2>\n<p>Let\u2019s imagine a group of attackers planning to remotely hack into an organization. They gather information about the given company, investigate its external perimeter, and perhaps even find employee credentials in databases of leaked passwords. But they find no exploitable vulnerabilities. Moreover, they discover that all of the company\u2019s external services are protected by two-factor authentication, so passwords alone aren\u2019t sufficient for access.<\/p>\n<p>One potential penetration method could be the corporate Wi-Fi network, which they could attempt to access using those same employee credentials. This applies especially if the organization has a guest Wi-Fi network that\u2019s insufficiently isolated from the main network\u00a0\u2014 such networks rarely use two-factor authentication. However, there\u2019s a problem: the attackers are on the other side of the globe and can\u2019t physically connect to the office Wi-Fi.<\/p>\n<p>This is where the Nearest Neighbor tactic comes into play. If the attackers conduct additional reconnaissance, they\u2019ll most likely discover numerous other organizations whose offices are within the Wi-Fi signal range of the target company. And it\u2019s possible that some of those neighboring organizations are significantly more vulnerable than the attackers\u2019 initial target.<\/p>\n<p>This may simply be because these organizations believe their activities are less interesting to cyberattack operators \u2014 leading to less stringent security measures. For example, they might not use two-factor authentication for their external resources. Or they may fail to update their software promptly \u2014 leaving easily exploitable vulnerabilities exposed.<\/p>\n<p>One way or another, it\u2019s easier for the attackers to gain access to one of these neighboring organizations\u2019 networks. Next, they need to find within the neighbor\u2019s infrastructure a device connected to the wired network and equipped with a wireless module, and compromise it. By scanning the Wi-Fi environment through such a device, the attackers can locate the SSID of the target company\u2019s network.<\/p>\n<p>Using the compromised neighboring device as a bridge, the attackers can then connect to the corporate Wi-Fi network of their actual target. In this way, they get inside the perimeter of the target organization. Having achieved this initial objective, the attackers can proceed with their main goals\u00a0\u2014 stealing information, encrypting data, monitoring employee activity, and more.<\/p>\n<h2>How to protect yourself against the Nearest Neighbor attack<\/h2>\n<p>It\u2019s worth noting that this tactic has already been used by at least one APT group, so this isn\u2019t just a theoretical threat. Organizations that could be targeted by such attacks should start treating the security of their wireless local area networks as seriously as the security of their internet-connected resources.<\/p>\n<p>To protect against the Nearest Neighbor attack, we recommend the following:<\/p>\n<ul>\n<li>Ensure that the guest Wi-Fi network is truly isolated from the main network.<\/li>\n<li>Strengthen the security of corporate Wi-Fi access\u00a0\u2014 for instance, by using two-factor authentication with one-time codes or certificates.<\/li>\n<li>Enable two-factor authentication \u2014 not only for external resources but also for internal ones, and, in general, adopt the <a href=\"https:\/\/www.kaspersky.com\/blog\/zero-trust-security\/36423\/\" target=\"_blank\" rel=\"noopener nofollow\">Zero Trust<\/a> security model.<\/li>\n<li>Use an advanced threat detection and prevention system, such as <a href=\"https:\/\/www.kaspersky.co.in\/next?icid=in_kdailyplacehold_acq_ona_smm__onl_b2b_kdaily_wpplaceholder_sm-team___knext____ece28c88d9230f31\" target=\"_blank\" rel=\"noopener\">Kaspersky Next XDR Expert<\/a>.<\/li>\n<li>If you lack highly qualified in-house cybersecurity specialists, make use of external services such as <a href=\"https:\/\/www.kaspersky.co.in\/enterprise-security\/managed-detection-and-response?icid=in_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder_______\" target=\"_blank\" rel=\"noopener\">Managed Detection and Response<\/a> and <a href=\"https:\/\/www.kaspersky.co.in\/enterprise-security\/incident-response?icid=in_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder_______\" target=\"_blank\" rel=\"noopener\">Incident Response<\/a>.<\/li>\n<\/ul>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"mdr\">\n","protected":false},"excerpt":{"rendered":"<p>We discuss the recently discovered Nearest Neighbor attack method, which enables attackers to compromise a Wi-Fi network from the other side of the world.<\/p>\n","protected":false},"author":2726,"featured_media":28375,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2036,2609],"tags":[1181,111,82,187,1196,3420,174,1913],"class_list":{"0":"post-28374","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-enterprise","9":"tag-2fa","10":"tag-attacks","11":"tag-hacking","12":"tag-passwords","13":"tag-routers","14":"tag-two-factor-authentication","15":"tag-wi-fi","16":"tag-wireless-networks"},"hreflang":[{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/nearest-neighbor-wi-fi-attack\/28374\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/nearest-neighbor-wi-fi-attack\/23632\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/nearest-neighbor-wi-fi-attack\/28504\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/nearest-neighbor-wi-fi-attack\/38738\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/nearest-neighbor-wi-fi-attack\/52763\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/nearest-neighbor-wi-fi-attack\/28631\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/nearest-neighbor-wi-fi-attack\/34458\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/nearest-neighbor-wi-fi-attack\/34082\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.in\/blog\/tag\/wi-fi\/","name":"wi-fi"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/28374","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/users\/2726"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/comments?post=28374"}],"version-history":[{"count":0,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/28374\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media\/28375"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media?parent=28374"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/categories?post=28374"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/tags?post=28374"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}