Google Chrome users who visit the Breitbart.com website today are receiving a warning message: “The Website Ahead Contains Malware!”

And Google’s widely-used search engine attaches a similar warning message to Breitbart.com: “This site may harm your computer.”

A lot of readers are justifiably concerned:

wow – that's weird…my chrome is blocking the breitbart sites because of suspected malware..and it just happened. — Rosalie Stuplich (@xanpixsmom) February 4, 2013

Chrome is blocking the breitbart site because of suspected malware! While NY Times seems unaffected, seems odd and fishy. — 1984 (@Animal1984Farm) February 4, 2013

Chrome is blocking access to Breitbart sites as having malware. Has Goggle Chrome been hacked? — Gene Young (@firefighterCOL) February 4, 2013

Naturally, liberals are delighted:

Google Chrome thinks that Andrew Breitbart's gango of mouthbreathers is malware. I agree. http://t.co/iONEJQ0i — Dheeraj Chand (@dheerajchand) February 4, 2013

LOL. All the Breitbart sites have been marked as Malware: http://t.co/Y7yDzl6W — John Whitehouse (@existentialfish) February 4, 2013

Because libs are happiest when conservatives can’t disseminate their views.

At least two Twitter users say the Google “malware” designation is incorrect:

@verytari It's not malware. I just proceeded through it. It's fine that messages comes up all over the place when it's wrong. It's Breitbart — Chris (@Chris_1791) February 4, 2013

Unless its deeper than I felt like looking, #Breitbart.com is NOT hosting malware. @BreitbartNews @HatingBreitbart — Alex P Keaton (@I_Hate_Hippies) February 4, 2013

Twitter user @NiceDeb says the Breitbart technical team is working on a fix:

@breitbart.com is fixing the Malware problem. Site should be back up on Firefox and Chrome soon,. — Nice Deb (@NiceDeb) February 4, 2013

Whatever the problem is, we hope it will be fixed soon.

Update:

We are apparently being hit by the same bug that caused the Super Bowl blackout ;). We've been working on it; meantime IE or Safari work OK. — Joel Pollak (@joelpollak) February 4, 2013

Update: We suspected this might be the case: