Seems nothing more than a direct redirect, but there could be a way of checking the referring URL to return a different output for the user; unless Google is reporting an issue that has been cleaned up already…
Thanks for checking on this one.
Last time Google Safe Browsing found this site malicious was on 30-11-2012.
And you are right, because the malware survived just 3.4 hrs before being closed. That was from 2012-12-02 23:01:04 to 2012-12-03 02:25:22 to be precise, that totalled up to 3.4 hrs. The payload in the attack was logged as being `/tmp/BARTChw5e’, alas this is history now. BARTChw apparently as origin of this attack…
So we can establish here the ever changing, sometimes short lived nature, presence of malcode on websites.
Logging attack codes like sites like on bizimbal dot com and IDS alerts like those on urlquery dot net could be analyzed for dominating malware attack patterns to be recognized…