Thank you. I see it now.
The problem has definitely been fixed by a subsequent update. Pretty quick work by MalWareBytes people.