Google developer publishes tool to report if Chrome extension has been hijacked – Computer – News

The article here now uses the terms “Google developer” and “Google developer”. This may be a misunderstanding because a Google developer expert (GDE). This means that he knows more than the average person about certain topics, but not that he works for Google.

I find the situation here wonderful. the The project's Github page indicates It uses the ExBoost API Server. Another repository from the same organization Describe ExBoost as a network through which add-ons can be promoted. Show blog The most visible promotion is possible for a fee. Furthermore, a couple of weeks ago I received unsolicited emails asking me to integrate ExBoost into my Chrome extensions, mentioning its name and GDE status to build trust.

The idea of ​​the extension is good, but I wonder what the motivations for publishing the extension and making it widely known in the news are.

Here are some corrections to the Tweakers article.

To the record He claims that the Chrome development team is also already working on making this detection a standard part of the browser's Web Extensions API.

This is an incorrect interpretation of the last paragraph in the record. Discussion of the idea in the broader browser and extension developer community is encouraged. This is not the same Chrome developers implementing the idea. Here you can find the general discussion that started as a result of this encouragement: https://github.com/w3c/webextensions/issues/558

“Also, Manifest does not take into account whether the new update is not necessarily malicious, but could export or misuse user data, or insert ads,” he adds.

This is a mistranslation of “What's more, this does not take into account cases where the new update is not necessarily harmful, (…)”. The word “this” here does not refer to the “statement” (which has no meaning in this context), but rather to the detection system that is supposed to detect malicious behavior.