diff --git a/.gitignore b/.gitignore deleted file mode 100644 index b50ae36..0000000 --- a/.gitignore +++ /dev/null @@ -1,10 +0,0 @@ -.DS_Store -*.crx -*.pem -*.zip -.idea/ -.vscode/ -*.swp -*.swo -*~ -.claude/ diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 604ebff..0000000 --- a/LICENSE +++ /dev/null @@ -1,21 +0,0 @@ -MIT License - -Copyright (c) 2019 Mo'men Basel - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. diff --git a/PRIVACY.md b/PRIVACY.md deleted file mode 100644 index c0a4a3d..0000000 --- a/PRIVACY.md +++ /dev/null @@ -1,61 +0,0 @@ -# Privacy Policy - KeyFinder Chrome Extension - -**Last Updated:** April 7, 2026 - -## Overview - -KeyFinder is a browser extension that scans web pages for leaked API keys, tokens, and secrets. This privacy policy explains how the extension handles data. - -## Data Collection - -KeyFinder does **not** collect, transmit, or share any personal data or browsing data with external servers. The extension operates entirely on your local device. - -## What Data is Stored Locally - -The extension stores the following data locally on your device using Chrome's built-in storage API (`chrome.storage.local`): - -- **Search keywords**: User-configured keywords used to identify potential secrets on web pages. -- **Scan findings**: When a potential secret is detected, the extension stores the pattern name, severity level, matched value, page URL, and domain where it was found. - -This data never leaves your device. - -## How Data is Processed - -- All page scanning happens locally within your browser. -- The extension reads page content (scripts, meta tags, form fields, HTML comments, browser storage, and network responses) to match against known secret patterns. -- No page content, scan results, or browsing activity is sent to any external server, API, or third party. - -## Data Sharing - -KeyFinder does **not** share any data with third parties. Specifically: - -- No data is sold to third parties. -- No data is used for advertising or marketing purposes. -- No data is transferred to third parties for reasons unrelated to the extension's core functionality. -- No analytics, telemetry, or tracking is implemented. - -## Data Retention - -All stored data remains on your local device until you choose to delete it. You can clear all findings at any time using the "Clear All" button in the findings dashboard. Uninstalling the extension removes all stored data. - -## Permissions - -- **activeTab**: Used to access the current page's content for scanning when the extension is active. -- **storage**: Used to save your keyword preferences and scan findings locally. -- **Host permissions**: The extension runs on all URLs because leaked secrets can appear on any website. No data from these pages is transmitted externally. - -## Third-Party Services - -KeyFinder does not integrate with, connect to, or send data to any third-party services. - -## Changes to This Policy - -Any changes to this privacy policy will be reflected in the extension's GitHub repository and the "Last Updated" date above. - -## Contact - -If you have questions about this privacy policy, contact the developer: - -- GitHub: [github.com/momenbasel](https://github.com/momenbasel) -- X: [@momenbassel](https://x.com/momenbassel) -- LinkedIn: [linkedin.com/in/momenbasel](https://www.linkedin.com/in/momenbasel/) diff --git a/README.md b/README.md deleted file mode 100644 index 0308118..0000000 --- a/README.md +++ /dev/null @@ -1,135 +0,0 @@ -
-
-
- Passive API key and secret discovery for Chrome -
- -
-
-
-
-
-
-
+ A Chrome extension that scans every page you visit for API keys, tokens, and credentials. + 80+ patterns. 10 attack surfaces. Zero config. +
+ + + +Install once. Every page you visit is automatically scanned for leaked secrets across all attack surfaces.
+Covers cloud providers, payment platforms, communication tools, AI services, databases, SaaS, infrastructure keys, crypto secrets, and generic patterns.
+Scans script URLs, inline scripts, external JS, meta tags, hidden form fields, data attributes, HTML comments, URL parameters, web storage, and network responses.
+Calculates Shannon entropy for detected strings. High-entropy values get flagged as likely secrets, reducing false positives on random-looking tokens.
+Pure vanilla JavaScript. No external libraries, no build step, no framework. Lightweight, fast, and auditable. Just the extension code and nothing else.
+Built on the latest Chrome extension architecture with a service worker. Future-proof, secure, and compatible with all modern Chromium browsers.
+Professional dashboard with filtering, sorting, and search. Export findings as JSON or CSV. Badge counter on the extension icon shows live results.
+From cloud provider keys to cryptocurrency wallet seeds, keyFinder recognizes credentials across the entire modern stack.
+Every page load triggers a comprehensive scan across all the places where secrets commonly leak.
+Examines URLs in script tags for embedded API keys and tokens passed as query parameters.
+Parses all inline JavaScript blocks on the page for hardcoded credentials and secret assignments.
+Fetches and analyzes external JavaScript files loaded by the page for leaked keys and tokens.
+Inspects meta tag content attributes where configuration keys and tokens are sometimes exposed.
+Scans hidden input fields that developers use to pass tokens and API keys through forms.
+Checks HTML data-* attributes where frontend frameworks often store configuration secrets.
+Extracts and scans HTML comments for accidentally committed credentials and debug tokens.
+Analyzes query strings and URL fragments for API keys and authentication tokens passed in the clear.
+Monitors localStorage and sessionStorage for secrets stored client-side by web applications.
+Intercepts XHR and Fetch responses to detect secrets returned by APIs and backend services.
+Two ways to install. Both take less than 60 seconds. No build tools required.
+chrome://extensionsgit clone https://github.com/momenbasel/keyFinder.gitchrome://extensionskeyFinder directoryInstall keyFinder and let it passively scan every page you visit. No configuration needed.
+ +