According to Brave Search (Answer with AI):
The #brave-extension-malware-blocklist flag enables Brave’s component-delivered malware list to be enforced as BLOCKLISTED_MALWARE through the browser’s existing Safe Browsing path.
This mechanism disables malicious extensions identified in Brave’s internal list, treating them with the same severity as extensions flagged by Google Safe Browsing.
By integrating this list into the upstream Blocklist, Brave ensures that extensions known to handle credentials improperly or violate user safety policies are automatically disabled upon detection - providing an additional layer of protection against supply chain attacks and hijacked extensions.
(AI-generated answer. Please verify critical facts.)
Where does Brave obtain the data for this list?
According to Brave Search (Answer with AI):
The data comes from Socket (socket.dev), a security research company that publishes threat intelligence on malicious browser extensions. Specifically, per GitHub issue #59814:
“This will be a component containing extension IDs provided by Socket and packed by brave-core-crx-packager, and delivered to clients like a normal CRX component.”
The pipeline works like this:
-
Socket supplies the list of malicious extension IDs based on their research.
-
The IDs are packed into a CRX component by brave-core-crx-packager.
-
The component is uploaded to Brave’s component update server (go-updater.brave.com) with the actual file stored in S3 (brave-core-ext.s3.brave.com).
-
The client ingests the list via the standard component updater mechanism, just like ad-block filters or tracking protection lists.
So it’s a first-party Brave component whose contents originate from Socket’s threat intelligence, not from Google Safe Browsing or any public community list.
(AI-generated answer. Please verify critical facts.)
Does it supplement Google Safe Browsing, or does it operate independently?
According to Brave Search (Answer with AI):
It supplements Google Safe Browsing rather than operating independently. The key detail from the PR is that it injects Socket’s list into the same upstream Chromium Blocklist code path, assigning the BLOCKLISTED_MALWAREverdict so enforcement (disabling the extension, showing the warning in brave://extensions) is identical to how Google’s own Safe Browsing extension list works.
In other words:
-
Same enforcement mechanism - both lists converge on the same BLOCKLISTED_MALWAREstate in extensions/browser/blocklist.cc.
-
Different data source - Google’s list arrives via the Safe Browsing Update API (proxied through safebrowsing2.brave.com), while Socket’s list arrives as a Brave-delivered CRX component.
-
Complementary coverage - the Brave wiki explicitly frames it as a second mechanism: “There are two ways that extensions are blocked in Brave: via Google Safe Browsing, and via a Brave-controlled mechanism.” The Socket-sourced list catches extensions that Google hasn’t (yet) flagged or that remain available on the Chrome Web Store.
So if a user disables Safe Browsing in settings, the Google-sourced list goes away, but the Socket-sourced component list is still enforced through the same code path - making it partially independent in terms of data availability, but not in terms of enforcement.
(AI-generated answer. Please verify critical facts.)