It strikes me that the best way to combat this might be in the browser itself - intercept and remove the offending javascript (or better, redirect its execution into a walled sandbox where it thinks it's setting cookies and downloading code) and remove it from the main page viewing stream.