Chrome threw a malware error
 

See attached image.

I received this yesterday and didn't really know what to do about it except "proceed with caution"

A'right, fess up. Who put something questionable in their sig files?

What the heck is a malware error, anyway?

My files are being violated!

I'm sure it's related to one of the advertisements. I've had that come up in the past but not in ages since I've been using adblock & whatnot.

It's very unlikely to be caused by an advertisement. The only advertising publisher we use is Google, and they carefully screen all ads that are displayed on this site (not to mention the fact that they are the same company that created Chrome).

Most likely, someone posted an image hosted on the site mentioned in the error (boonage.pj...). If anyone notices a particular thread or post where this is happening, please let me know.

Whoever's sig is hosting the malware posted on this page of this thread, because it's where I met the same warning a moment ago-

http://forums.thetechnodrome.com/sho...16#post1262116

Yup. Got the same error when clicking on Powders link.

Yep, I've just got the exact same warning. I wonder who's signature it is

It's yipster32

And yet Firefox says nothing... curious.

I don't think it is. I looked at the link on my Ipod touch, and it redirected me to one of Raph's posts.

Not trying to balme anyone, but that's what it directed me to.

Open that raph signature photo of his in another window. Look at the url.

See attached again

Oh right. It's just the link Powder provided directed me to Raph's post.

My bad.

Has anyone read the advanced info? The issue is the server network Rutger's collection site is running through. It's being flagged because other sites utilizing the same network have been flagged for suspicious content. Rutger is not giving anybody malware, though you may increase the chance of inviting it by being on his sites network. The server is across the Atlantic and touches god knows how many different networks getting to your computer screen. Ah, the risks of hosting...

Thanks for helping me track this down, everyone. The problem should be corrected now.