We’ve determined that this issue is caused by a change in Virudie’s API response.
Please see this announcement for more information: