{"id":5649,"date":"2024-10-04T15:30:33","date_gmt":"2024-10-04T20:30:33","guid":{"rendered":"https:\/\/www.darkreading.com\/cyber-risk\/malicious-chrome-extensions-past-google-updated-security"},"modified":"2024-10-04T15:30:33","modified_gmt":"2024-10-04T20:30:33","slug":"malicious-chrome-extensions-skate-past-googles-updated-security","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/10\/04\/malicious-chrome-extensions-skate-past-googles-updated-security\/","title":{"rendered":"Malicious Chrome Extensions Skate Past Google’s Updated Security"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

Malicious browser extensions are bypassing Google’s latest security and privacy standard for Chrome extensions, and they are finding their way into the Chrome Web Store \u2014<\/span> <\/span><\/span>putting organizations and individuals at considerable risk.<\/span><\/p>\n

That’s according to researchers at Singapore-based SquareX, who recently demonstrated how bad actors could sneak harmful browser add-ons past the protections in Google’s latest Manifest V3 update for Chrome extensions.<\/span><\/p>\n

Malicious Chrome Extensions Are a Continuing Problem<\/h2>\n

In a presentation at DefCon 32, the <\/span>researchers showed<\/a><\/span> how such extensions could steal live video feeds from platforms like Google Meet and Zoom without requiring any special permissions. They then demonstrated how attackers could use extensions based on the Manifest V3 standard to redirect users to credential-stealing pages, add collaborators to private GitHub repos, and steal site cookies, browsing history, and other user data relatively easily.<\/span><\/p>\n

Google introduced <\/span>Manifest V3<\/a><\/span> in 2018 to address issues in the previous Manifest V2 standard, which more easily allowed bad actors to craft Chrome extensions with a range of malicious capabilities. A study by <\/span>researchers at Stanford University<\/a><\/span> concluded that there were a staggering 280 million installs of such malicious Chrome extensions between July 2020 and February 2023.<\/span><\/p>\n

Related:<\/span>Dark Reading Confidential: The CISO and the SEC<\/a><\/p>\n

As Google explains it, Manifest V3 is part of a broader effort by the company to “improve the privacy, security, and performance of extensions.” Improvements in Manifest V3 include a stricter content security policy, updated and more secure APIs, more granular permission control for users, and changes to how extensions can make cross-origin requests. Some of the updates, like one that changes how Chrome handles content-blocking extensions, have been controversial. <\/span>Privacy advocates<\/a><\/span> and makers of ad-blocking extensions have described the feature as drastically curtailing the ability for Chrome users to block ads and tracking mechanisms. But overall, the goal with Manifest V3 is improved security and privacy controls around Chrome extensions.<\/span><\/p>\n

The ground reality is somewhat different, says Vivek Ramachandran, CEO and founder of SquareX. “[Manifest V3’s] permission model remains too broad, allowing malicious actors to exploit minimal permissions to steal data,” he says.<\/span><\/p>\n

Overly Broad Permissions for Manifest V3?<\/h2>\n

A key example is host permissions that allow an extension to modify or read any Web content on visited pages. “SquareX demonstrated a Google Meet stream-stealing extension that only required host permission,” Ramachandran says. “This type of permission is very common in the extension store. In fact, many extensions, like grammar checkers, rely on it.”<\/span><\/p>\n

Related:<\/span>Name That Edge Toon: And For My Next Trick …<\/a><\/p>\n

Ramachandran estimates there are already hundreds if not thousands of malicious browser extensions based on Manifest V3 that are already in the Chrome Web Store. He expects that number to increase dramatically as more extensions cut over to Manifest V3.<\/span><\/p>\n

“Google needs to enforce stricter security controls in MV3,” Ramachandran says. “They should collaborate with the Web and security community to develop a more robust permission model that is less broad. Additionally, Google should improve the vetting process for extensions and introduce tools to monitor real-time behavior.”<\/span><\/p>\n

Google did not immediately respond to a Dark Reading request for comment on SquareX’s research. But the Internet giant previously has conceded that with more than 250,000 browser extensions in Chrome Web Store, there are chances some extensions could pose risks to users and sometimes request permissions that might violate a company’s policies.  <\/span><\/p>\n

“As with any software, extensions can also introduce risk,” Google said in a <\/span>blog post<\/a><\/span> shortly after the Stanford researchers released their paper on risky extensions in the Chrome Web Store.<\/span><\/p>\n

Related:<\/span>iPhone ‘VoiceOver’ Feature Could Read Passwords Aloud<\/a><\/p>\n

Boosting Chrome Ecosystem Security<\/h2>\n

In that blog post and in previous updates, <\/span>like this one in April 2023,<\/a><\/span> Google has highlighted its efforts to bolster security around Chrome extensions. These include browser extension management capabilities that security teams can use to view and set policies for all installed extensions in their environment, and the ability to review extensions before users can install them.<\/span><\/p>\n

Chrome security features also include one that alerts admins when a user might install a new browser extension, to make tracking and management easier. And last year, Google introduced two risk assessment tools \u2014 <\/span>CRXcavator<\/a><\/span> and <\/span>Spin.AI Risk Assessment<\/a><\/span> \u2014 that give enterprise admins a way to assess and score extensions for risk.<\/span><\/p>\n

Google also points to its Chrome extensions page (chrome:\/\/extensions\/) as a resource that individuals can use to see if their installed extensions pose a security risk; a warning panel appears on the page if Google detects any installed extensions as being suspicious. That definition includes: browsers suspected of containing malware; browsers that violate Chrome Web Store polices; unpublished \u2014 and therefore no longer supported extensions; and extensions that are not explicit about their privacy and data-collection practices.<\/span><\/p>\n

Google had set a <\/span>deadline of this past June<\/a><\/span> for browser extension makers to migrate to Manifest V3 and has noted that it would also begin disabling Manifest V2 extensions in its pre-stable versions of Chrome at that time. The company has given enterprise organizations until June 2025 to migrate Manifest V2 extensions to the new version. As of Oct. 4, 60.4% of all Chrome browser extension have <\/span>migrated to Manifest V3<\/a><\/span>.<\/span><\/p>\n

Ramachandran says enterprises should audit installed extensions and limit their permissions. His advice is that organizations also enable better visibility and control over extensions in the environment. Think of browsers like Chrome as complex platforms, much like operating systems, he suggests.<\/span><\/p>\n

“Extensions run as internal applications, but endpoint security tools only have visibility at the process level,” Ramachandran says. “They cannot assess or control what browser extensions are doing internally.”<\/span><\/p>\n

Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Malicious browser extensions are bypassing Google’s latest security and privacy<\/p>\n","protected":false},"author":12,"featured_media":5650,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[809],"class_list":["post-5649","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-dark-reading"],"featured_image_urls":{"full":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?fit=1920%2C1080&ssl=1",1920,1080,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?fit=1536%2C864&ssl=1",1536,864,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?fit=1920%2C1080&ssl=1",1920,1080,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?fit=1024%2C576&ssl=1",1024,576,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?resize=825%2C575&ssl=1",825,575,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?resize=590%2C410&ssl=1",590,410,true]},"author_info":{"display_name":"Dark Reading","author_link":"https:\/\/ddi.mohflo.net\/index.php\/author\/darkreading\/"},"category_info":"Uncategorized<\/a>","tag_info":"Uncategorized","comment_count":"0","jetpack_featured_media_url":"https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/10\/malicious-chrome-extensions-skate-past-googles-updated-security.jpg?fit=1920%2C1080&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/5649","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/comments?post=5649"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/5649\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/5650"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=5649"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=5649"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=5649"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}