![]() ![]() I am curious to know if people who've had compromised extensions were to DELETE them (not just disable them) and then re-install them from the store, if the superfish code immediately reappears. The other alternative is that there is a, as of yet unknown virus, that is able to manipulate the code of a number of different extensions without the user (or developer) knowing anything about it. If anything, it's a big hats-off to ABP for making us aware of this garbage. Thus, exposing how many extensions were really loaded with malware/adware. ![]() Then perhaps with one of the most recent filter updates for ABP, it finally started jamming the communications between the malicious code and the superfish servers. I'm thinking they've been rogue for quite a while, and no one knew. Seems awfully suspicious that so many developers would sell out to superfish, and then all of them go "live" with this bug at the same time. I do wonder about the timing of all of these extensions going rogue at the same time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |