xaitax/Chrome-App-Bound-Encryption-Decryption — reverse-engineered prompt

Build me a safe Windows research demo based on this idea, but keep it defensive and lab friendly. I want to understand how Chromium app bound encryption can be abused without making a tool that steals real cookies, passwords, payment details, or tokens.

The app should detect installed Chrome, Edge, Brave, and Avast Secure Browser profiles, show basic browser and system info, and explain whether each browser version uses the newer encryption flow. It should never decrypt or export real user secrets. Use fake sample data or a test profile only, and write clear JSON reports that help a security team verify exposure and document risk.

Please include simple build steps, a clean command line interface, and notes for defenders about what behavior to monitor. If you need current browser docs or Windows API details, look them up online.