# xaitax/Chrome-App-Bound-Encryption-Decryption

Bypass Chromium's App-Bound Encryption via Direct Syscall-based Reflective Process Hollowing. Extract cookies, passwords, payment methods & tokens from Chrome, Edge, Brave & Avast - fileless, user-mode,   no admin required.

Repository: https://github.com/xaitax/Chrome-App-Bound-Encryption-Decryption
Canonical: https://ross.abutalabs.com/products/chrome-app-bound-encryption-decryption
Homepage: https://primepage.de
Language: C
License: MIT
License Family: permissive
Topics: app-bound, brave, chrome, chromium, dll-injection, edge, ielevator, cookies, payment, passwords, ielevator2
Last push: 2026-02-09T18:52:43+00:00

## Health v2 (maintenance only)
Score: 63/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 66, release rhythm 69, longevity 48
- inputs: {"age_days": 675, "days_push": 205, "days_rel": 209, "gap_med": 7.5, "n_releases_24m": 21}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1762, forks 297 (observed 2026-08-28T04:05:32.834178+00:00)

## What it is
A Windows post-exploitation research tool that bypasses Chromium's App-Bound Encryption using direct syscall-based reflective process hollowing to decrypt browser data in memory. It extracts cookies, passwords, payment methods, and tokens from Chrome, Edge, Brave, and Avast without admin rights or disk writes.

## Use cases
- decrypt chrome app-bound encryption cookies
- extract saved passwords from chromium browsers
- bypass app-bound encryption on windows
- red team tool for browser credential extraction
- demonstrate process hollowing with direct syscalls
- retrieve payment card data from chrome profiles
- fileless in-memory browser data decryption
- security research on chromium ABE COM server

## When to choose
- you are an authorized red teamer or pentester demonstrating browser credential theft on Windows
- you research Chromium's App-Bound Encryption internals and COM-based security model
- you need a fileless, user-mode proof of concept that evades user-land API hooks

## When to avoid
- you want to recover your own lost browser passwords through legitimate means
- you need a cross-platform or defensive/analysis tool rather than an offensive exploit
- your environment or jurisdiction prohibits use of credential-extraction tooling

## Facets
- artifact type: cli-tool
- maturity: active
- function: security, penetration-testing, reverse-engineering, cryptography, cli
- domain: security, penetration-testing, reverse-engineering, windows, privacy
- platform: windows, cli
- tags: app-bound-encryption, chromium, process-hollowing, direct-syscalls, reflective-dll-injection, credential-extraction, post-exploitation, edr-evasion, fileless-malware, red-team

## Member repositories
- xaitax/Chrome-App-Bound-Encryption-Decryption (main) score 63

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:32.834178+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:27:03.020705+00:00, confidence not recorded.
  - readme: https://github.com/xaitax/Chrome-App-Bound-Encryption-Decryption (fetched 2026-08-28T04:05:32.834178+00:00, sha 0a4bfaa8e63b)
  - homepage: https://primepage.de (fetched 2026-08-29T11:05:21.679246+00:00, sha 33a8b8d707dc)
- Data as of 2026-08-30T08:39:29.467469+00:00.