It is the dll that is malicious. The installer probably had some functions (for reason unknown) in a module next to it. The attackers replaced the dll with a malicious one. When the installer calls the function as it normally would, it becomes a conduit for the malware. So Norton is right, the file is indeed trusted. The Symantec engines were much better at detecting sideloading.The link is detected by Norton and its family, but the malicious fake Chrome Updater is not detected.

