Experimental Chrome Manifest V3 extension for browser-fingerprint modification, privacy instrumentation, and synthetic interaction testing.
Phantom Identity explores how a browser extension can modify selected fingerprinting surfaces in the page context while providing a small dashboard and verification pages for observing the resulting browser state.
Scope: This is an academic / portfolio prototype. It is not an anonymity system and does not guarantee protection against sophisticated fingerprinting, tracking, anti-fraud, or bot-detection systems.
| Area | Implementation |
|---|---|
| Extension platform | Chrome / Chromium Manifest V3 |
| Page-context injection | injected-script.js |
| Fingerprint surfaces | Navigator, screen/timezone, Canvas, WebGL, hardware-related properties |
| Settings/state | chrome.storage |
| Behavioral experiment | Synthetic mouse-movement and smooth-scroll events |
| UI | Extension popup with settings, current fingerprint state, and privacy score |
| Verification | Local fingerprint and injection test pages |
The injected page-context layer can override selected Navigator and related properties using a generated spoof configuration, including user-agent/platform-style fields and hardware-related values.
When enabled, the extension wraps Canvas readout paths such as toDataURL, toBlob, and getImageData and applies small pixel-level changes before fingerprint-relevant output is returned.
The extension wraps WebGL/WebGL2 getParameter calls for selected renderer/vendor values when WebGL spoofing is enabled.
The content script can generate periodic synthetic mouse-movement and smooth-scroll events. This is included as an experimental behavioral-obfuscation mechanism; the project does not claim that these events defeat production behavioral biometrics or bot-detection systems.
The popup exposes feature toggles and displays current fingerprint-related state, a project-defined privacy score, and fingerprint-change statistics.
Manual test pages are included under tests/manual/ for inspecting navigator values, Canvas behavior, WebGL values, and injection behavior.
Chrome / Chromium
|
v
Manifest V3
|
+-----------------------+
| |
v v
background.js content-script.js
settings / state document-start injection
| |
+-----------+-----------+
|
v
injected-script.js
|
+--------+--------+
| | |
v v v
Navigator Canvas WebGL
popup.html / popup.js
|
v
settings + current state + project privacy score
The extension uses a background service worker, a document-start content script, and a web-accessible injected script so that selected browser APIs can be modified in the page's main execution context.
Phantom_Identity/
├── .github/workflows/ # Repository validation CI
├── docs/ # Installation, project notes, and SRS
├── icons/ # Extension icons
├── tests/manual/ # Browser-based verification pages
├── background.js # Service worker and project state
├── content-script.js # Injection + behavioral experiment
├── injected-script.js # Page-context API modifications
├── manifest.json # Manifest V3 configuration
├── popup.html
├── popup.css
├── popup.js
├── index.html # Local project/demo page
├── server.py # Optional local helper server
└── README.md
- Open Chrome or another Chromium-based browser.
- Navigate to
chrome://extensions/. - Enable Developer mode.
- Choose Load unpacked.
- Select this repository directory.
See docs/INSTALLATION.md for the original project installation notes.
The repository includes local test pages under tests/manual/.
Useful checks include:
- navigator / platform values;
- Canvas output changes;
- WebGL vendor / renderer values;
- page-context injection behavior;
- popup state and feature toggles.
These tests demonstrate that the implemented hooks are active in the tested browser setup; they are not a comprehensive measurement of real-world tracking resistance.
The extension requests broad host access because the prototype was designed to test page-context behavior across sites. That permission is security-sensitive and should be narrowed before any production distribution.
Important limitations:
- changing fingerprint attributes can itself create unusual or inconsistent fingerprints;
- browser APIs and anti-fingerprinting techniques evolve over time;
- Canvas/WebGL modification does not imply anonymity;
- synthetic interaction events do not prove resistance to behavioral profiling;
- the project has not been independently evaluated against production anti-fraud systems;
- the project-defined privacy score is a local heuristic, not an external privacy benchmark;
- some sites may behave differently or break when browser properties are modified.
The implementation was originally developed separately from this public portfolio repository. The extension source is now included here so that the repository reflects the implementation described in the documentation.
Replit metadata, generated assets, and development-prompt artifacts from the original working directory are intentionally excluded.
docs/INSTALLATION.md— original installation notesdocs/PROJECT_SUMMARY.md— original project summarydocs/software-requirements-specification.docx— software requirements specification
Phantom Identity is intended for browser-security, privacy, and software-engineering experimentation on systems you own or are authorized to test.
Do not represent this prototype as providing guaranteed anonymity, guaranteed anti-fingerprinting protection, or guaranteed bypass of fraud/bot-detection systems.