how do I remove Stags,bluekai.com pop up when using ebay

Hi, as I posted before, that was also my first response to the bluekai problem. I upgraded to High Sierra and it got rid of that problem. But it created other problems (VGA display link stopped functioning). That was when I contacted Apple Support, who after a couple phone calls told me there was no way to restore VGA display and to go back to my old system. Apple Support, incidentally, was nice and willing but essentially offered no practical help. IT was after restoring my 10.9.5 that I found the advice about Avast. Which, I repeat, is not a great solution but better than nothing. What I have not tried it so upgrade to say, 10.10; just for lack of time and energy.

The last time I upgraded, some older programs and applications would not work, it was a pain to get everything back working. So I'm hesitant also, but I'm going to back up my drive and do it. Thanks for your post, 5 stars to you.

Just want to let everyone know - the upgrade to High Sierra worked fine, it did get rid of the annoying BlueKai issue (which was really my driving issue). And apparently now offers a superior level of protection in general. Everything is working ok - other than one fault. The screen saver no longer kicks in when the Mac is not in use. Previously it would after 20 mins. This seems to be a common and widespread issue after upgrading. (Check out the forums/google).

Frankly I can live with it. I tend to put the Mac to 'sleep' anyway once I'm finished. It wakes up ok.

I've not yet contacted Apple Support re this, but will get round to it.

So I do appreciate the concerns and issues relating to upgrading as are reported by others.

However - BlueKai is gone!

Hope the upgrade works for others.

KevJD wrote:

Just want to let everyone know - the upgrade to High Sierra worked fine

Upgrading to High Sierra is a good thing, security-wise. However, you should be aware that the jump from 10.9 to 10.13 is a huge one! That's akin to upgrading your car's stereo from an 8-track to a touch-screen CD-MP3 console. Not only are you going to have issues with your accessories (all your existing 8-track tapes will need to be replaced with something newer), there's some question about whether a car old enough to have an 8-track can even work with such a new console.

Similarly, with an upgrade from 10.9 to 10.13, you're almost guaranteed to have some apps that you rely on stop working and require a paid upgrade or outright replacement. You also need to think about not just whether High Sierra is compatible with your older Mac, but also whether it's advisable to run it. For example, High Sierra's new APFS filesystem is not advised for use on Macs with rotational hard drives, and it will run slower than the HFS+ filesystem used by Sierra and earlier. An SSD is really needed for High Sierra.

Be sure to do your homework before upgrading, or you may find you've traded this annoying issue with something more Earth-shattering.

Avast worked for me for a week or so, then stopped. The blue.akai virus is back. Has Apple addressed this issue with a software patch or even looked at it and offered their own advice? Come on Apple!! A virus on a MAC! On your own browser program, SAFARI! I miss Steve Jobs.

I don't know if anyone's considered the possibility this annoying pop up virus originated from Apple as another way of pushing users to upgrade. I am another anti icloud person and it's getting more and more difficult to have free choice.

I've seriously considered it. The way Apple has been acting since Cook took the reins, it wouldn't surprise me one bit. They've lost their focus.... and show nothing but disdain for long-time Apple users. (btw, I couldn't even find your comment "helpful", StarEv. SMH.

Little by little Apple is losing me. I did the same thing (switched to Firefox) and the problem went away. I'm also looking at alternatives to iTunes, which Apple completely destroyed for some unknown reason.

thanks thomas_r. for the comprehensive and thoughtful reply. I believe you. So I upgraded to Mac OS X 10.13 and I have what appears to be a brand new machine and, importantly, I can browse ebay without that stupid stags.bluekai.com pop up popping up. Of course an OS upgrade is not for the faint of heart, it took over 2 hours.

Here is how I fixed the stags.bluekai.com issue on my OSX 10.9 in seconds without installing software or updates but first some details:

As other mentioned before the message appear because the Oracle https certificate expired in January.

And who has in stalled AVAST is not getting the error because it is facing https certificates to the browser as others also already mentioned.

But the root of the cause is that websites like eBay have links to stags.bluekai.com in there pages with no obvious use for the user.

So here is the trick: enter in the console "sudo vi /etc/hosts" or use an editor of your choice.

And add the following line (at to bottom if you want): "127.0.0.1 stags.bluekai.com".

That's it! And happy surfing!

By the way you should add some more websites in this way to your /etc/hosts that are linked in websites nowadays without any use for the user.

After a blissful 2 months of Avast preventing the stags.bluekai.com security notice, it's back. I have followed other instructions for elimination, but the instructions just don't line up with my Mac's configuration. As I have High Sierra on a new iMac, and it runs the programs I use the most, I think (hope) I will not have issues with the update.

HI, I had gotten rid of bluekai using Avast but now it is back.

If I go in Terminal and perform your PING procedure I get an apparently endless series of PING sequences that looks like this, what do you recommend?

64 bytes from 104.123.24.239: icmp_seq=0 ttl=54 time=2.656 ms

64 bytes from 104.123.24.239: icmp_seq=1 ttl=54 time=2.984 ms

64 bytes from 104.123.24.239: icmp_seq=2 ttl=54 time=3.343 ms

64 bytes from 104.123.24.239: icmp_seq=3 ttl=54 time=3.433 ms

64 bytes from 104.123.24.239: icmp_seq=4 ttl=54 time=3.289 ms

64 bytes from 104.123.24.239: icmp_seq=5 ttl=54 time=3.851 ms

64 bytes from 104.123.24.239: icmp_seq=6 ttl=54 time=3.242 ms

64 bytes from 104.123.24.239: icmp_seq=7 ttl=54 time=2.745 ms

64 bytes from 104.123.24.239: icmp_seq=8 ttl=54 time=3.423 ms

64 bytes from 104.123.24.239: icmp_seq=9 ttl=54 time=3.341 ms

64 bytes from 104.123.24.239: icmp_seq=10 ttl=54 time=3.185 ms

64 bytes from 104.123.24.239: icmp_seq=11 ttl=54 time=2.487 ms

64 bytes from 104.123.24.239: icmp_seq=12 ttl=54 time=3.326 ms

64 bytes from 104.123.24.239: icmp_seq=13 ttl=54 time=3.359 ms

64 bytes from 104.123.24.239: icmp_seq=14 ttl=54 time=3.313 ms

64 bytes from 104.123.24.239: icmp_seq=15 ttl=54 time=3.145 ms

64 bytes from 104.123.24.239: icmp_seq=16 ttl=54 time=3.044 ms

64 bytes from 104.123.24.239: icmp_seq=17 ttl=54 time=3.154 ms

64 bytes from 104.123.24.239: icmp_seq=18 ttl=54 time=3.039 ms

64 bytes from 104.123.24.239: icmp_seq=19 ttl=54 time=2.493 ms

64 bytes from 104.123.24.239: icmp_seq=20 ttl=54 time=2.361 ms

64 bytes from 104.123.24.239: icmp_seq=21 ttl=54 time=2.198 ms

64 bytes from 104.123.24.239: icmp_seq=22 ttl=54 time=2.465 ms

64 bytes from 104.123.24.239: icmp_seq=23 ttl=54 time=3.063 ms

64 bytes from 104.123.24.239: icmp_seq=24 ttl=54 time=3.009 ms

64 bytes from 104.123.24.239: icmp_seq=25 ttl=54 time=3.009 ms

64 bytes from 104.123.24.239: icmp_seq=26 ttl=54 time=2.274 ms

64 bytes from 104.123.24.239: icmp_seq=27 ttl=54 time=3.240 ms

64 bytes from 104.123.24.239: icmp_seq=28 ttl=54 time=3.115 ms

64 bytes from 104.123.24.239: icmp_seq=29 ttl=54 time=3.095 ms

64 bytes from 104.123.24.239: icmp_seq=30 ttl=54 time=3.941 ms

64 bytes from 104.123.24.239: icmp_seq=31 ttl=54 time=2.332 ms

64 bytes from 104.123.24.239: icmp_seq=32 ttl=54 time=3.302 ms

64 bytes from 104.123.24.239: icmp_seq=33 ttl=54 time=2.984 ms

64 bytes from 104.123.24.239: icmp_seq=34 ttl=54 time=2.318 ms

64 bytes from 104.123.24.239: icmp_seq=35 ttl=54 time=2.556 ms

64 bytes from 104.123.24.239: icmp_seq=36 ttl=54 time=2.123 ms

64 bytes from 104.123.24.239: icmp_seq=37 ttl=54 time=3.192 ms

64 bytes from 104.123.24.239: icmp_seq=38 ttl=54 time=2.896 ms

64 bytes from 104.123.24.239: icmp_seq=39 ttl=54 time=3.000 ms

64 bytes from 104.123.24.239: icmp_seq=40 ttl=54 time=3.210 ms

64 bytes from 104.123.24.239: icmp_seq=41 ttl=54 time=3.125 ms

64 bytes from 104.123.24.239: icmp_seq=42 ttl=54 time=2.228 ms

64 bytes from 104.123.24.239: icmp_seq=43 ttl=54 time=3.187 ms

64 bytes from 104.123.24.239: icmp_seq=44 ttl=54 time=3.171 ms

64 bytes from 104.123.24.239: icmp_seq=45 ttl=54 time=2.823 ms

64 bytes from 104.123.24.239: icmp_seq=46 ttl=54 time=2.295 ms

64 bytes from 104.123.24.239: icmp_seq=47 ttl=54 time=2.339 ms

64 bytes from 104.123.24.239: icmp_seq=48 ttl=54 time=2.700 ms

64 bytes from 104.123.24.239: icmp_seq=49 ttl=54 time=3.161 ms

64 bytes from 104.123.24.239: icmp_seq=50 ttl=54 time=2.951 ms

64 bytes from 104.123.24.239: icmp_seq=51 ttl=54 time=3.079 ms

64 bytes from 104.123.24.239: icmp_seq=52 ttl=54 time=2.972 ms

64 bytes from 104.123.24.239: icmp_seq=53 ttl=54 time=3.231 ms

64 bytes from 104.123.24.239: icmp_seq=54 ttl=54 time=3.407 ms

64 bytes from 104.123.24.239: icmp_seq=55 ttl=54 time=2.921 ms

64 bytes from 104.123.24.239: icmp_seq=56 ttl=54 time=2.501 ms

64 bytes from 104.123.24.239: icmp_seq=57 ttl=54 time=3.116 ms

64 bytes from 104.123.24.239: icmp_seq=58 ttl=54 time=2.464 ms

64 bytes from 104.123.24.239: icmp_seq=59 ttl=54 time=3.001 ms

64 bytes from 104.123.24.239: icmp_seq=60 ttl=54 time=3.021 ms

64 bytes from 104.123.24.239: icmp_seq=61 ttl=54 time=2.509 ms

64 bytes from 104.123.24.239: icmp_seq=62 ttl=54 time=2.610 ms

64 bytes from 104.123.24.239: icmp_seq=63 ttl=54 time=3.004 ms

64 bytes from 104.123.24.239: icmp_seq=64 ttl=54 time=3.061 ms

64 bytes from 104.123.24.239: icmp_seq=65 ttl=54 time=2.772 ms

64 bytes from 104.123.24.239: icmp_seq=66 ttl=54 time=2.431 ms

This is very interesting. I am having the issue on my my mac. I have mavericks 10.9. I do not want to upgrade because my mac only has 8 gb of ram and only a 1.4ghz i5. I switched to firebox because it still receives updates for my system but I am having the blukai pop up in Firefox as well. It seems to happen at random on any website I go to.

Update on this issue: now Safari gets pop up for lots of websites when I try to access - "cannot verify website xxx" this is always a totally unrelated site, nothing to do with what I'm accessing.

Firefox does not get this problem at all. It seems no one has found a solution that is reliable. Any new ideas out there?

None of this worked for me. I can't delete the website from history as I never opened the website. I'm getting an "invalid certificate" pop up for this site that will not go away.