{"id":22944,"date":"2018-07-03T10:44:51","date_gmt":"2018-07-03T14:44:51","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=22944"},"modified":"2019-11-15T06:35:34","modified_gmt":"2019-11-15T11:35:34","slug":"preventing-dangerous-screenshots","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/preventing-dangerous-screenshots\/22944\/","title":{"rendered":"The mystery of the black square"},"content":{"rendered":"<p>Hi folks!<\/p>\n<p>Can you guess what this is? It\u2019s not a vandalized version of Malevich\u2019s <a target=\"_blank\" href=\"https:\/\/en.wikipedia.org\/wiki\/Black_Square_(painting)\" rel=\"noopener noreferrer nofollow\">Black Square<\/a>.<\/p>\n<p>That black box is \u2014 more or less \u2014 what a screenshot taken by a suspicious application on a computer protected by Kaspersky Lab products, for example, <a href=\"https:\/\/www.kaspersky.com\/total-security?icid=gl_kdailyplacehold_acq_ona_smm__onl_b2c_kasperskydaily_wpplaceholder____kts___\" target=\"_blank\" rel=\"noopener nofollow\">Kaspersky Total Security<\/a>, looks like. Why?<\/p>\n<p>Our products protect screenshots because cybercriminals \u2014 and other cyberlowlifes \u2014 are <em>really<\/em> interested in getting access to user accounts. The reasons vary (money, espionage, <a target=\"_blank\" href=\"https:\/\/en.wikipedia.org\/wiki\/Herostratus\" rel=\"noopener noreferrer nofollow\">Herostratic<\/a> delusions of grandeur, spying on spouses\/competitors\/enemies, etc.), and the intruders use different means, but the end they seek is always the same: access to user accounts.<\/p>\n<p>But, you may be wondering, why does malware want to take screenshots? Sites and software products substitute dots for the characters used in a password, so what\u2019s the point?<\/p>\n<p>Actually, there are plenty of ways to get around those dots.<\/p>\n<p>First, users often have the option to see the entered password (\u201cshow password\u201d or some such). Second, many services <em>always<\/em> show the last few symbols of a password. Third, some services replace the password with dots only when the user proceeds to the next entry field.<\/p>\n<p>Fourth, some services do not use masking dots at all, instead making the font size of the password field tiny \u2014 the idea is to make the password illegible to someone close by (unfortunately, that\u2019s no deterrent to malware). Fifth, a variety of <a target=\"_blank\" href=\"https:\/\/lifehacker.com\/5946529\/easily-reveal-hidden-passwords-in-any-browser\" rel=\"noopener noreferrer nofollow\">lifehacks<\/a> and tools (like pwdcrack) let baddies turn off password-masking dots. All in all, the likelihood that a password will be shown on a screen is far from zero, and malware easily exploits that fact.<\/p>\n<p>Incidentally, the likelihood of someone looking over your shoulder, or of security cameras taking a peek at your password, is negligible compared with the threat of it being read by malware using a screenshot.<\/p>\n<p>Probably the most well-known banking Trojan, Zeus \u2014 as well as many of its <a target=\"_blank\" href=\"https:\/\/www.kaspersky.com\/blog\/atmos-yet-another-zeus-variant-is-threatening-businesses\/5476\/\" rel=\"noopener noreferrer nofollow\">clones<\/a> \u2014 includes this function in its tool set. For example, one of those clones, named <a target=\"_blank\" href=\"https:\/\/threatpost.com\/kins-banking-trojan-a-successor-to-citadel\/101440\/\" rel=\"noopener noreferrer nofollow\">KINS<\/a>, conducts an attack that takes screenshots not just when keys are pressed, but also when the mouse is clicked. That is, even if a virtual keyboard is used on a banking website for entering passwords or one-time codes, the malware can still work out the entered symbols.<\/p>\n<p>It\u2019s not just passwords, though. How about bank card details entered when buying something online? What about the security questions you\u2019re asked for authentication or to recover access to a locked account? Personal information? Message contents? The list goes on and on.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kis-trial-privacy\">\n<p>Indeed, the humble screenshot is a major gateway to our private information and secrets; as such, protecting the information a screenshot can provide to outsiders is critical. Using functions such as <a target=\"_blank\" href=\"https:\/\/eugene.kaspersky.com\/2012\/08\/14\/safe-money-online-banking-security\/\" rel=\"noopener noreferrer\">Safe Money<\/a> and <a target=\"_blank\" href=\"https:\/\/www.kaspersky.com\/blog\/how-and-why-you-should-use-the-virtual-keyboard\/3040\/\" rel=\"noopener noreferrer nofollow\">Virtual Keyboard<\/a> help, of course, but not everyone uses them \u2014 even some who consider themselves security-conscious. And anyway regular cybersecurity functions cannot guarantee total protection when cybervillains still have screenshotting in their arsenal. But we\u2019re ready and waiting for them.<\/p>\n<p>Most of our products include a patented technology that guards the <a target=\"_blank\" href=\"https:\/\/en.wikipedia.org\/wiki\/Application_programming_interface\" rel=\"noopener noreferrer nofollow\">API<\/a> functions that allow applications to take screenshots. Thus, if an application is trying to take a screenshot, this is what happens:<\/p>\n<ul>\n<li>The product works out which applications have windows open;<\/li>\n<li>Based on data from various components and subsystems (for example <a target=\"_blank\" href=\"https:\/\/eugene.kaspersky.com\/2011\/09\/15\/features-youd-normally-never-hear-about\/\" rel=\"noopener noreferrer\">System Watcher<\/a>and <a target=\"_blank\" href=\"https:\/\/www.kaspersky.com\/about\/press-releases\/2015_kaspersky-lab-s-safe-money-technology-recognized-as-outstanding-by-mrg-effitas\" rel=\"noopener noreferrer nofollow\">Safe Money<\/a>), the product determines if these windows potentially contain confidential or personal data;<\/li>\n<li>The product analyzes the trust rating of the applications that request access to the screen;<\/li>\n<li>The product decides whether to allow screenshots. If not, screenshots will get the black-square treatment.<\/li>\n<\/ul>\n<p>And last but not least: a bonus!<\/p>\n<p>The same technology that protects against malicious screenshotting is also helping detect previously unknown cyberattacks. Applications that suspiciously show an interest in other \u201cwindows,\u201d seemingly without any real purpose, have their rating lowered, bringing them closer to being proactively detected by <a target=\"_blank\" href=\"https:\/\/www.kaspersky.com\/blog\/what-humachine-intelligence-is\/17995\/\" rel=\"noopener noreferrer nofollow\">machine learning<\/a> through <a target=\"_blank\" href=\"https:\/\/eugene.kaspersky.com\/2012\/09\/18\/crowdsourcing-security\/\" rel=\"noopener noreferrer\">KSN<\/a> \u2014 or detected manually by an expert. That way, little by little, with a truly global effort plus highly trained cyberbrains, we all together lower the overall danger level of the Internet for the benefit of everyone.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It\u2019s not Malevich\u2019s Black Square. This is what a screenshot taken by a suspicious application on a computer protected by Kaspersky Lab products looks like.<\/p>\n","protected":false},"author":13,"featured_media":22945,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[7,1789],"tags":[522,192,2972,1083,422],"class_list":{"0":"post-22944","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-products","8":"category-technology","9":"tag-products-2","10":"tag-protection","11":"tag-screenshots","12":"tag-technologies","13":"tag-threats"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/preventing-dangerous-screenshots\/22944\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/preventing-dangerous-screenshots\/13594\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/preventing-dangerous-screenshots\/11348\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/preventing-dangerous-screenshots\/15654\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/preventing-dangerous-screenshots\/13897\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/preventing-dangerous-screenshots\/13121\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/preventing-dangerous-screenshots\/16399\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/preventing-dangerous-screenshots\/15887\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/preventing-dangerous-screenshots\/20862\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/preventing-dangerous-screenshots\/5075\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/preventing-dangerous-screenshots\/10685\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/preventing-dangerous-screenshots\/10472\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/preventing-dangerous-screenshots\/9350\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/preventing-dangerous-screenshots\/17141\/"},{"hreflang":"zh","url":"https:\/\/www.kaspersky.com.cn\/blog\/preventing-dangerous-screenshots\/9737\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/preventing-dangerous-screenshots\/20787\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/preventing-dangerous-screenshots\/16903\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/preventing-dangerous-screenshots\/20523\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/preventing-dangerous-screenshots\/20514\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/products-2\/","name":"products"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/22944","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\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=22944"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/22944\/revisions"}],"predecessor-version":[{"id":29693,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/22944\/revisions\/29693"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/22945"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=22944"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=22944"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=22944"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}