Show HN: Daily-updated database of malicious browser extensions(github.com)
github.com
Show HN: Daily-updated database of malicious browser extensions
https://github.com/toborrm9/malicious_extension_sentry
8 comments
Nice work. One thing I've noticed with locally checking extensions against threat lists is that the verification process itself can become a target. Stateless, deterministic verification — where hashes or IDs are derived on-device and never stored centrally — reduces risk of supply chain or server-side compromise. It’s a subtle design point, but it can prevent a malicious actor from using the verification system itself to exfiltrate data.
Great point. The current setup is exactly what you're describing, a fully local verification with no phone-home behavior.
The CLI/GUI tools I'm building read your locally installed extensions, extract their IDs, and check them against the CSV (which you can clone/download). No data leaves your machine during the scan.
The only "central" piece is the GitHub-hosted CSV itself, which is just a static file anyone can audit, fork, or host themselves. No API calls, no telemetry, no server lookups.
You're right that this design prevents the verification tool from becoming an attack vector. Even if my repo got compromised, worst case is a bad CSV, your local scan process stays isolated.
I'm also looking at surfacing critical permissions for locally installed extensions,things like "access to all websites," "read clipboard," etc. That way users can make informed decisions about what to keep based on what's actually authorized, even if an extension isn't in the malicious database yet.
Appreciate the security-minded feedback.
The CLI/GUI tools I'm building read your locally installed extensions, extract their IDs, and check them against the CSV (which you can clone/download). No data leaves your machine during the scan.
The only "central" piece is the GitHub-hosted CSV itself, which is just a static file anyone can audit, fork, or host themselves. No API calls, no telemetry, no server lookups.
You're right that this design prevents the verification tool from becoming an attack vector. Even if my repo got compromised, worst case is a bad CSV, your local scan process stays isolated.
I'm also looking at surfacing critical permissions for locally installed extensions,things like "access to all websites," "read clipboard," etc. That way users can make informed decisions about what to keep based on what's actually authorized, even if an extension isn't in the malicious database yet.
Appreciate the security-minded feedback.
It appears that some of the extensions in your block list originate from a supply chain attack which compromised some extensions, but which have since been fixed and are no longer compromised and have returned the Chrome store. This post discusses matching both the ID and version to detect compromised extensions without creating false positives.
For example, only v4.00 of Bookmark Favicon Changer was compromised. Earlier and later versions are clean.
https://www.elastic.co/blog/how-to-detect-malicious-browser-...
For example, only v4.00 of Bookmark Favicon Changer was compromised. Earlier and later versions are clean.
https://www.elastic.co/blog/how-to-detect-malicious-browser-...
Super cool, I hope this gets the attention it deserves!
The database updates automatically by monitoring chrome-stats for removed extensions and scanning security blogs. Currently tracking 1000+ known malicious extensions with extension IDs, names, and dates.
I'm working on detection tools (GUI + CLI) to scan locally installed extensions against this database, but wanted to share the raw data first since maintained threat intelligence lists like this are hard to find.
The automation runs 24/7 and pushes updates to GitHub. Free to use for research, integration into security tools, or whatever you need.
Happy to answer questions about the scraping approach or data collection methods.