Mozilla adds Ubisoft Uplay to the blocklist

Martin Brinkmann
Jul 31, 2012
Updated • Nov 25, 2012

When Mozilla detects serious security or stability issues in add-ons or plugins, it may decide to block them for all users of the browser. A security vulnerability has recently been discovered in Ubisoft's Uplay software which can be exploited by third parties. The majority of online magazines and reports call it a rootkit, which is not the really the term that should be used to describe the software. Unlike rootkits, the program does not attempt to hide the functionality on the system, and it is much more likely that it is simply code that has not been tested enough.

When PC users install a Ubisoft game that makes use of the UPlay networking service, a browser plugin may be installed on the system as part of the process. It is not really clear what the plugin is being used for at all, and disabling it should not have any effect on the games requiring UPlay.

As far as games go, it is used by Assassin's Creed games, Homam VI, the Tom Clancy series and several other games. It may also depend on where you have purchased the game on, as some versions of the mentioned games may come without Uplay after all.

Sites like Rock Paper Shotgun quickly advised users to turn off the plug-in in their web browser of choice

  • Firefox: about:addons – Plugins – Disable the Uplay and Uplay PC Hub plugins
  • Chrome: Visit about:plugins and disable
  • Opera: Settings – Preferences – Advanced – Downloads – Search “Uplay”, delete
  • Internet Explorer:  Press Alt, then Tools > Manage Add-ons, and disable UPlay there.

Reports suggest that Ubisoft may have resolved the issue by pushing out an update to Uplay that brings the version of the application to 2.04.  At the time of writing, it is however not clear if the update resolves the issue completely.

Mozilla in the meantime has added Ubisoft Uplay to the blocklist of the Firefox browser which effectively blocks the plugin from being loaded when the browser starts. Being on the blocklist furthermore blocks the plugin from being installed in the browser.

I'd still recommend to remove the plugin from any browser it may be installed in just to be on the safe side.


Previous Post: «
Next Post: «


There are no comments on this post yet, be the first one to share your thoughts!

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.