New Supply Chain Attack Vector just dropped: falsely report a single package on a package repository website as being malicious to the Google Safe Browsing List, and they will block the entire freaking domain! Chrome, Firefox, and Brave, all use the Google Safe Browsing API to warn users if they're about to visit a malicious domain, and make it difficult to override. Lots of other websites/services also use the Google Safe Browsing List/API to filter links, such as Reddit, Blogger, and Google Workplaces / GMail.
This literally just happened today to the metasploit-payloads gem (last version released on May 8th, 2023) on https://rubygems.org and took several hours to resolve. During which time, users got a giant red warning screen when visiting rubygems.org, new Reddit comments linking to rubygems.org got auto-removed, Blogger automatically flagged/removed old blog posts that contained rubygems.org links, the Ruby Weekly newsletter got flagged by Google Workplaces as containing malware because it linked back to rubygems.org, and a few people on Twitter reported DNS issues with their CI server because they were using Google Safe Browsing List to filter DNS domains.
Now imagine if someone falsely reported pwntools on PyPi to the Google Safe Browsing List? Imagine how much disruption that would cause to the Python ecosystem if suddenly https://pypi.org started getting flagged as malicious by the Google Safe Browsing List? Imagine the confusion and frustration when people's Reddit comments and Blogger posts started getting auto-removed?
Yeah, maybe Google should add a new policy for handling abuse reports about packages on package repository websites, like not flagging the entire domain, or better yet forward the abuse reports to the website's admins and let them review the package in question.
#supplychain #supplychainsecurity #googlesafebrowsing #rubygems #pypi #npm #cratesio