I been having this problem after updating AVAST to the lastest version.
It seems like AVAST is recognizing this file playercore-4.0001.627.034[1].js as a malware.
Now, I have contacted Netflix and they say many people had same trouble just like me(with AVAST).
I added Netflix as an exclusion, but that doesn’t seems like its working.
Unless I can solve this issue in this Forum, they leave me no choice, but to uninstall.
So please help
You can report a suspected FP here: https://www.avast.com/false-positive-file-form.php
The guys from netflix apparently use some very advanced obfuscation techniques (perhaps to bypass adblock?), some that are used by authors of malware since 2013. Avast saw the known obfuscation technique, which was the reason of this false positive.
In our stats, it seems like they stopped using this file yesterday evening, so everything should be ok now. Can you confirm?
Let us know if the problem still persist, and I will see what I can do 
Yes! I just checked and it has been resolved!!! Thank you!
Hi all. I been having this problem after updating AVAST to the lastest version. My AVAST is recognizing several Netflix playercore files as a malware. I know that this problem has been spoken about before and was deemed resolved but not for me. My system and access to Netflix was working fine last night but then this morning after an update to Avast when trying to access Netflix Avast keeps coming up with two different errors. For playercore-4.0001.627.034[1].js I get JS:Agent-CPN and for playercore 3.0003.237.011.js|{gzip} I get JS:Redirector-BKD I am running Windows 8.1 Pro and have tried accessing Netflix with both Chrome and Internet Explorer. I even deleted my version of Avast and installed a clean version. Any suggestions? I have no Netflix access.
Same story as before - they are using the same obfuscation some rather prevalent malware is using. Most likely they (Netflix) will notice that they are blocked by AVs, so they should change it rather quickly. Right now I can see a decrease in hit counts for these 2 detections, so perhaps they changed it already?
Hi,
I have the same problem with netflix. I am using Chrome on a macbook pro, and I do not use an adblock. It works fine with Safari though…