Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

Malicious Chrome Extension Poses As Facebook Video

As malware attacks targeting browser extensions become more common, security researchers advise users to be more careful about installing extensions and to regularly review permissions.

Beware an attack campaign that pretends to offer a Facebook video but instead installs a malicious extension in Chrome Web browsers.

That warning was sounded this week by Kaspersky Lab, which said that it had spotted variations of that attack being hosted on the official Google Chrome Web store. Some versions of the attack, which originated in Turkey, are customized to target Italian users of Facebook, while other variations target Latin Americans.

"Attacks such as these ones are getting very common," Fabio Assolini, senior security researcher at Kaspersky Lab, said via email. He blamed users for too often not exercising good sense when it comes to adding extensions to their browser. "They need to know that an extension can access everything you do in the browser, all the data, passwords and the websites visited, so it's very important to not install unknown extensions," he said. "The situation gets worse when the malicious extension is hosted in the official Chrome Web store, as we noticed in some attacks."

[ Are Gmail users entirely too trusting? Read Gmail Is Not A Privacy Problem. ]

As with the Android security model, the Chrome browser lists which permissions any Chrome extension will be granted should a user allow it to be installed. Assolini recommended that all Chrome users regularly review the extensions they have installed, as well as the permissions they'd been granted. "Avoid installing those asking [for too many] permissions to access personal data," he advised.

The fake Facebook video attack campaign isn't the first time users have been targeted by malicious Chrome extensions. A particularly large campaign was spotted last year that targeted people in Brazil -- where Chrome's installation base is now 65%, according to StatCounter -- via malicious extensions distributed by the Chrome Web store.

Assolini said there's a constant "cat and mouse game" between cybercriminals, who upload malicious extensions to the Chrome Web store and attempt to trick people into installing them, and Google, which removes the extensions whenever it learns they're there.

The Chrome extension security situation improved after June 2012, however, when Google updated Chrome to prevent it from running any extension that wasn't procured from the Chrome Web store, and required users to navigate to their browser's "extensions" page to add any extension. Google explained that it made the change because it doesn't have the ability to take down malicious items promoted on other websites, meaning hackers could have launched attacks that silently installed extensions that would then monitor all Web traffic and information flowing to or from a browser.

At the same time it announced that change, Google also revealed that it had begun scanning extensions for signs of maliciousness. "To help keep you safe on the Web, we have started analyzing every extension that is uploaded to the Web Store and take down those we recognize to be malicious," the company said.

Still, some information security experts see a lingering Chrome extension security risk, since they're set to automatically update. For example, if an attacker was able to compromise an updated extension prior to its distribution, they'd have a prebuilt mechanism for injecting malicious JavaScript into the browser of any user that had installed the extension. In corporate environments, it's unlikely that antivirus tools would spot any such malicious activity since malicious extensions would be handling only HTTP requests and JavaScript code and would thus appear normal.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16248
PUBLISHED: 2020-08-09
** DISPUTED ** Prometheus Blackbox Exporter through 0.17.0 allows /probe?target= SSRF. NOTE: follow-on discussion suggests that this might plausibly be interpreted as both intended functionality and also a vulnerability.
CVE-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
CVE-2020-15821
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, a user without permission is able to create an article draft.
CVE-2020-15823
PUBLISHED: 2020-08-08
JetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
CVE-2020-15824
PUBLISHED: 2020-08-08
In JetBrains Kotlin before 1.4.0, there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.