Fact Checked by Irfan Ahmad.
Many Google's Blogger.com users began reporting that their blogs had returned online on Aug. 5 after a widespread wave of malware-policy lockouts disrupted access to sites across multiple countries. Some users, however, said their blogs were removed again shortly after being restored, leaving questions over what triggered the incident.
Image: Blogger.com web interface for locked accounts. Credit: DIW, CC BY.
A Blogger Product Expert published a support thread at about 1:10 a.m. Pakistan time on Aug. 5 after numerous users reported their blogs had been locked under Blogger's "Malware and Similar Malicious Content" policy.
The Product Expert said the large number of reports appeared to involve automated misclassification rather than genuine malware violations, adding that the Blogger team had been notified and advising affected users to submit a Request Review.
In a statement to DIW, a Google spokesperson said, "We are aware of a bug that incorrectly flagged some Blogger-hosted sites as malware for less than a day. We are working on a fix to resolve the issue as quickly as possible."
The issue quickly drew widespread attention. By the time this article was published, the support thread had attracted 359 "I have the same question" responses along with dozens of comments from affected users. A separate Reddit discussion filled with similar reports as bloggers and creators exchanged updates and compared their experiences.
The reports came from publishers running news, educational, travel, photography, review and personal blogs. Many said their websites had operated for years without previous malware-related policy issues before suddenly becoming inaccessible.
For much of the day, the discussion centered on uncertainty.
Users repeatedly asked when reviews would be completed, whether the issue was affecting everyone, and if their blogs would return. Several said the malware notification made it appear that they had committed a confirmed policy violation before they later discovered that many other publishers were reporting the same problem.
As the hours passed, recovery reports gradually began replacing new complaints.
Several Reddit users posted that their blogs had returned, with comments including, "Mine's fixed!", "One of my blogs is back online" and "Yesterday was removal. Today is reinstatement. No appeal sent." Others urged fellow publishers to back up their content immediately after regaining access.
Not every recovery lasted.
Some Blogger users reported that their blogs were restored after review only to be removed again under the same malware policy without any further changes. Others said their blogs briefly reappeared before disappearing once more, while some commenters earlier said they were still waiting for their sites to be restored.
The incident also prompted criticism of how it was communicated.
Several users said they struggled to understand what had happened after receiving emails stating that their blogs violated the malware policy. One commenter described the support thread as the first "official-sounding explanation" they had found after hours of searching. Others called for clearer communication, more detailed explanations and faster updates while their review requests remained pending.
Some questioned whether automated systems should be able to suspend blogs without stronger human oversight. Others wrote that the uncertainty had left them worried about years of work stored on their blogs, while a number of commenters said they hoped Blogger would explain what had happened once the incident was resolved.
Although many blogs appeared to be returning, Google had not published a broader public explanation beyond the Product Expert's statement that the reports appeared to involve automated misclassification.
Google responded to DIW with a brief statement confirming the issue was caused by a bug. "We can confirm the bug is now fixed and all sites have been reinstated," the spokesperson said. The tech giant did not address several additional questions, including what caused the bug, whether it had determined if any external activity, including a cyberattack, hacking attempt or abuse campaign, played a role, how many blogs were affected, what steps were being taken to help prevent similar incidents and whether Google plans to continue supporting Blogger long term.
Update, August 6 and 7: Google statement.
Read next:
• Google's AI Search Has Struggled With One Religious Question for Years
• NYU Researchers Map Where U.S. Data Centers Are Located
Many Google's Blogger.com users began reporting that their blogs had returned online on Aug. 5 after a widespread wave of malware-policy lockouts disrupted access to sites across multiple countries. Some users, however, said their blogs were removed again shortly after being restored, leaving questions over what triggered the incident.
A Blogger Product Expert published a support thread at about 1:10 a.m. Pakistan time on Aug. 5 after numerous users reported their blogs had been locked under Blogger's "Malware and Similar Malicious Content" policy.
The Product Expert said the large number of reports appeared to involve automated misclassification rather than genuine malware violations, adding that the Blogger team had been notified and advising affected users to submit a Request Review.
In a statement to DIW, a Google spokesperson said, "We are aware of a bug that incorrectly flagged some Blogger-hosted sites as malware for less than a day. We are working on a fix to resolve the issue as quickly as possible."
The issue quickly drew widespread attention. By the time this article was published, the support thread had attracted 359 "I have the same question" responses along with dozens of comments from affected users. A separate Reddit discussion filled with similar reports as bloggers and creators exchanged updates and compared their experiences.
The reports came from publishers running news, educational, travel, photography, review and personal blogs. Many said their websites had operated for years without previous malware-related policy issues before suddenly becoming inaccessible.
For much of the day, the discussion centered on uncertainty.
Users repeatedly asked when reviews would be completed, whether the issue was affecting everyone, and if their blogs would return. Several said the malware notification made it appear that they had committed a confirmed policy violation before they later discovered that many other publishers were reporting the same problem.
As the hours passed, recovery reports gradually began replacing new complaints.
Several Reddit users posted that their blogs had returned, with comments including, "Mine's fixed!", "One of my blogs is back online" and "Yesterday was removal. Today is reinstatement. No appeal sent." Others urged fellow publishers to back up their content immediately after regaining access.
Not every recovery lasted.
Some Blogger users reported that their blogs were restored after review only to be removed again under the same malware policy without any further changes. Others said their blogs briefly reappeared before disappearing once more, while some commenters earlier said they were still waiting for their sites to be restored.
The incident also prompted criticism of how it was communicated.
Several users said they struggled to understand what had happened after receiving emails stating that their blogs violated the malware policy. One commenter described the support thread as the first "official-sounding explanation" they had found after hours of searching. Others called for clearer communication, more detailed explanations and faster updates while their review requests remained pending.
Running a blogger blog? Wow, seems that many got nuked yesterday which might be a giant false positive (from a security standpoint). Checking the thread, a number of blogs have been removed.
— Glenn Gabe (@glenngabe) August 5, 2026
If these are false positives, this is terrible for the site owners. Also a reminder… https://t.co/DaWOzE47ds pic.twitter.com/ZECJIoBXsG
Some questioned whether automated systems should be able to suspend blogs without stronger human oversight. Others wrote that the uncertainty had left them worried about years of work stored on their blogs, while a number of commenters said they hoped Blogger would explain what had happened once the incident was resolved.
Although many blogs appeared to be returning, Google had not published a broader public explanation beyond the Product Expert's statement that the reports appeared to involve automated misclassification.
Google responded to DIW with a brief statement confirming the issue was caused by a bug. "We can confirm the bug is now fixed and all sites have been reinstated," the spokesperson said. The tech giant did not address several additional questions, including what caused the bug, whether it had determined if any external activity, including a cyberattack, hacking attempt or abuse campaign, played a role, how many blogs were affected, what steps were being taken to help prevent similar incidents and whether Google plans to continue supporting Blogger long term.
Update, August 6 and 7: Google statement.
Read next:
• Google's AI Search Has Struggled With One Religious Question for Years
• NYU Researchers Map Where U.S. Data Centers Are Located
){kind=link}