Content Security Policy: Couldn’t parse invalid source chrome-extension

I solved this same problem for myself after recently posting it as a Facebook bug on https://developers.facebook.com/x/bugs/729597157070762/ With FB’s help I noticed the following unwanted browser extensions in Firefox: Searchme, Slick Savings, Amazon Shopping Assistant, and Ebay Shopping Assistant. Turns out these are essentially malware that effected Firefox, Safari, and Chrome on my Mac. They’re made by a company called Spigot, Inc.

While searching for an effective means of virus removal I found this link http://www.thesafemac.com/arg-spigot/ which gives detailed instructions how to do so.

I hope this helps you kevin!

Unfortunately a month or so after my original answer (above) the same error and warnings came back for me but just as of yesterday, 4/22/2014 they changed to these 5 warnings, instead:

1. Content Security Policy: allow directive is deprecated, use the equivalent

default-src directive instead

  ...conds();wa=na.getUTCMilliseconds();}na=(pa<=0||pa>=10000?(pa<0?"-":"+")+o(6,pa<0...
    all.js (line 27)

1. The X-Content-Security-Policy and X-Content-Security-Report-Only headers will be deprecated in the future. Please use the Content-Security-Policy and Content-Security-Report-Only headers with CSP spec compliant syntax instead.

2. “Content Security Policy: allow directive is deprecated, use the equivalent default-src directive instead”

3. “The X-Content-Security-Policy and X-Content-Security-Report-Only headers will be deprecated in the future. Please use the Content-Security-Policy and Content-Security-Report-Only headers with CSP spec compliant syntax instead.”

4. Use of getPreventDefault() is deprecated. Use defaultPrevented instead.

   {href:function(a){return a.getAttribute("href")},type:function(a){return a.getAt

   jquery.min.js (line 3)

My guess is that the errors/warnings are due to the way the Facebook like button is engineered and how it interacts with Firefox and other browsers. The change in warnings and errors to these new warnings seems to indicate that Facebook and or Mozilla are working on this issue and will hopefully fix it…???

yesterday, 4/29/2014 This was officially classified as a Facebook known bug issue I created and is currently being addressed. Below is text from the FB email to me:

The bug you are subscribed to “like button works but errors show onload in firebug “Content Security Policy: Failed to parse unrecognized source chrome-extension://lifbcibllhkdhoafpjfnlhfpfgnpldfl”” has been updated:
Status has changed: Closed → Assigned

Hi All, We have managed to reproduce this issue and it appears to be a valid bug. We are assigning this to the appropriate team. This might take some time to fix but we will do our best to keep you updated on the progress of this bug as soon as we can. Thanks

today, 5/07/2014 I just received an email from Facebook stating,

“Status has changed: Assigned → Fixed

This should now be resolved. Thanks for your patience.”

Looks good on my end, no longer an issue.