Show HN: Daily-updated database of malicious browser extensions

Tiny add‑ons, big trouble — users beg for Firefox & Brave support

TLDR: An open, daily-updated list now flags Chrome/Edge extensions removed for malware so people can spot bad add-ons fast. The comments cheer the effort but demand Firefox/Brave support and warn the checker itself must be “stateless” and local—especially after reports of extensions spying on chats and stealing keys.

Your cute little add‑ons might be snooping. A dev just dropped a daily‑updated database of Chrome/Edge extensions booted from the Chrome Web Store for malware and shady behavior—perfect timing after headlines about ChatGPT chat spies, stolen API keys, and a $6,000 “guaranteed” malware kit. For non‑tech readers: extensions are tiny tools for your browser; sometimes they go rogue. This list auto‑pulls removals from monitoring services, security blogs, and threat feeds, and exposes bad actors by ID, name, and date. Data ships in simple files (.csv, .md), with a no‑frills Mac checker coming soon. Applause? Yes. Panic? Also yes.

The sharpest comment came from KevinChasse, warning that “the verification process itself can become a target,” and pushing for stateless, on‑device checks that can’t be hijacked. Then the feature requests piled up: “Could Firefox extensions be included?” asked politelemon. “Brave support by any chance?” added julius, noting Linux found Chrome but not their main browser. The mood: we love it—now make it universal and bulletproof. Hype crew (“hope this gets the attention it deserves!”) mixed with gallows humor: extensions are the new exes—delete half and feel safer; check your Extensions tab like your bank statement. Translation: audit your add‑ons before they audit you.

Key Points

  • Automatically updated database tracks malicious Chrome/Edge extensions removed from the Chrome Web Store.
  • Data is aggregated from monitoring services, security research publications, and threat intelligence feeds.
  • Each entry includes extension ID, name, and date added for traceability.
  • Data is available in Markdown and CSV formats for research, vetting, and tool-building.
  • A Python tool for macOS is planned to locally check installed extensions; community contributions are invited, with a disclaimer about potential false positives.

Hottest takes

"the verification process itself can become a target" — KevinChasse
"Could Firefox extensions be included?" — politelemon
"Brave support by any chance?" — julius
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.