Name: FINGER
Rating: 5 (1 reviews)
Author: vortex

History

11 snapshots

Tracking since Apr 2, 2026.

View as table

Date	Users	Rating	Reviews	Version
Apr 2, 2026	49	5.00	1	1.2.3
Apr 17, 2026	44	5.00	1	1.2.3
Apr 23, 2026	40	5.00	1	1.2.4
Apr 27, 2026	43	5.00	1	1.2.4
May 5, 2026	50	5.00	1	1.2.5
May 10, 2026	51	5.00	1	1.2.5
May 16, 2026	57	5.00	1	1.2.5
May 22, 2026	48	5.00	1	1.2.5
May 29, 2026	56	5.00	1	1.2.5
Jun 4, 2026	64	5.00	1	1.2.5
Jun 10, 2026	60	5.00	1	1.2.5
Now	73	5.00	1	1.2.5

Changelog

Apr 27, 2026

description

🧿🌐FINGER – Live‑Time Browser Fingerprinting Shield
Protect your privacy at its deepest layer.
➡️ FINGER is a powerful Chrome extension designed to detect and block browser fingerprinting as it happens. Instead of relying on outdated blocklists, FINGER monitors actual behavior inside the browser—catching hidden tracking scripts that other tools miss.

Why Choose FINGER?
Browser fingerprinting allows websites to identify you by collecting subtle details about your device—even with cookies disabled. Most privacy tools never look at this layer of tracking.
FINGER changes that by offering:
🛡️ Live-Time Protection
Blocks fingerprinting attempts the moment they occur—before any identifying data leaves your browser.
🧠 Behavior-Based Detection
Finds fingerprinting scripts even when they’re obfuscated, dynamically injected, or designed to evade filter lists.
📊 Entropy Insights
Each attempt is analyzed and scored with an approximate entropy value, giving you visibility into how “unique” you appear.
🔒 100% Local & Private
All analysis happens directly in your browser.
No data is ever sent anywhere.
🔧 Minimal Permissions
Uses only what’s necessary (ActiveTab), reducing risk and aligning with best security practices.
🧩 Modular, Extensible Architecture
Easily add new detection or blocking rules—perfect for advanced users and researchers.
💻 Open Source
Community-driven, transparent, and available under the MIT license.

Key Features
⚡🔴 Live Fingerprinting Detection
Instantly see when a website tries to gather identifying metrics.
⚡🕵 Comprehensive JavaScript Interception
Monitors method calls, property access, and API usage linked to fingerprinting.
⚡📟 Clean, Intuitive Dashboard
View logs, entropy scores, and blocked attempts with ease.
⚡🎓 Research-Grade Toolkit
Built for privacy enthusiasts, academics, and developers auditing web applications.
⚡🔜 Future-Proof Design
Ready for upcoming enhancements, including iframe inspection and cross-browser support.

Who Is FINGER For?
👤 Privacy-Conscious Users
Block invisible tracking while browsing.
👨🏻‍🏫 Researchers & Educators
Study real-world fingerprinting techniques in controlled environments.
🙍🏻‍♂️ Web Developers
Audit your own sites for accidental or legacy fingerprinting logic.
👩🏼‍💻 Open-Source Contributors
Improve detection modules, extend coverage, and help the community grow.

How FINGER Works
➡️FINGER uses advanced JavaScript interception techniques, including:
🪖 Method Overriding
⛊ Property Redefinition
🤺Proxy Wrapping for Dynamic Objects

These techniques allow precise, live-time blocking without degrading your browsing experience.

How FINGER Compares
➡️ Tools like AdBlock Plus, uBlock Origin, Privacy Badger, and Disconnect rely on static filter lists.
FINGER complements them by targeting behavioural fingerprinting, a type of tracking most extensions do not inspect.

🔜 Future Roadmap
🌕Enhanced iframe and embedded context detection.
🔭Cross-browser compatibility (Firefox, Edge, Safari).
.𖥔 ݁ ˖ִ🛸༄˖°. Configurable user policy engine for custom blocking strategies.
🚀Integration with research platforms for large-scale studies.

Open Source & Community
Explore or contribute here:
🫂 https://github.com/vortexcolab

Changelog
v1.2.1 — Adjusted action height to 100% to ensure all content is fully visible.
v1.2.2 — Fix: Preserve original constructor prototype when wrapping constructors to avoid breaking built-ins.
v1.2.3 — Restore native Uint8Array via Reflect.construct to preserve original constructors/symbols and prevent uncaught TypeErrors.
v1.2.4 — Fix: Ensure Node.prototype.appendChild is intercepted instead of HTMLElement.prototype.appendChild to maintain correct prototype chain behavior and prevent breaking DOM operations in complex SPAs (e.g., Jira).