Sorry, I don't normally monitor WordPress.org support.
It is still unclear just how the site was hacked.
It is most unfortunate that the hack coincided with the release of Weaver II 2.0. Several people have mentioned to me that this may have been intentional.
Whatever, I've gotten the hack cleared, significantly minimized the number of plugins used by the site, and spent time hardening the site from future attacks.
But I would like to repeat - the Weaver II theme itself was not compromised, and the versions you can download from both here at WordPress.org and the Pro version are not compromised.
And a word about Wordfence - it checks files on your site for links to other sites - even down to checking for site names in code comments. If there is a link to a site listed by Google as bad, then you get a warning. Wordfence must be using a cached version of the Google list as it was still issuing warning long after Google had cleared weavertheme.com. If you followed the link back to the Google report, you would see the site was listed as okay again. I do wish that Wordfence would make it much more clear that YOUR site is okay in these cases - it is just a link to another site - and one that for the most part was probably hacked, and not one intentionally having badware.