Snapshot của moonD4rk/HackBrowserData: 14.7k★ · Go · Backend. Decrypt and export passwords, cookies, history and more from 20 browsers on Windows, macOS and Linux. For authorized security research, incident response and DFIR.
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
Decrypt and export passwords, cookies, history and more from 20 browsers on Windows, macOS and Linux.
Website · Docs · Download
HackBrowserData is a command-line tool for decrypting and exporting browser data (passwords, history, cookies, bookmarks, credit cards, download history, localStorage, sessionStorage and extensions) from the browser. It supports the most popular Chromium-based browsers and Firefox on Windows, macOS and Linux, plus Safari on macOS.
It can also decrypt data across machines and operating systems: export the master keys on the origin host, then decrypt a copy of the data offline on any other host — even for a browser that the analyst host's OS cannot run (see Cross-host decryption).
Disclaimer: This tool is only intended for security research. Users are responsible for all legal and related liabilities resulting from the use of this tool. The original author does not assume any legal responsibility.
Supported Data Categories
Category
Chromium-based
Firefox
Safari
Password
✅
✅
✅
Cookie
✅
✅
✅
Bookmark
✅
✅
✅
History
✅
✅
✅
Download
✅
✅
✅
Credit Card
✅
-
-
Extension
✅
✅
✅
LocalStorage
✅
✅
✅
SessionStorage
✅
-
-
Supported Browsers
On macOS, some Chromium-based browsers require a current user password to decrypt.
Password decryption may fail on macOS 26.4 or later.
Browser
Windows
macOS
Linux
Chrome
✅²
✅
✅
Chrome Beta
✅²
✅
✅
Chromium
✅
✅
✅
Edge
✅²
✅
✅
Brave
✅²
✅
✅
Opera
✅
✅
✅
OperaGX
✅
✅
-
Vivaldi
✅
✅
✅
Yandex
✅
✅
-
CocCoc
✅²
✅
-
Arc
✅
✅
-
DuckDuckGo³
✅
-
-
Browser from Vought³
✅
-
-
QQ³
✅
-
-
360 Speed X³
✅
-
-
360 Speed³
✅
-
-
DC³
✅
-
-
Sogou³
✅
-
-
Firefox
✅
✅
✅
Safari¹
-
✅
-
¹ Safari requires Full Disk Access; enable it in System Settings → Privacy & Security → Full Disk Access if extraction returns empty results.
² On Windows, decrypting Chromium 127+ cookies (Chrome / Chrome Beta / Edge / Brave / CocCoc) requires the App-Bound Encryption payload built via make build-windows — see Building from source below.
³ These browsers ship only on Windows, but their data is decryptable on any OS: pull the files with archive, export the keys with dumpkeys, then decrypt on macOS or Linux with restore — see Cross-host decryption.
Getting Started
Install
Installation of HackBrowserData is dead-simple, just download the release for your system and run the binary.
In some situations, this security tool will be treated as a virus by Windows Defender or other antivirus software and can not be executed. The code is all open source, you can modify and compile by yourself.
Building from source
Requires Go 1.20+.
git clone https://github.com/moonD4rk/HackBrowserData
cd HackBrowserData
go build ./cmd/hack-browser-data/
Cross-platform build
# For Windows (standard build, no Chromium 127+ ABE cookie support)
GOOS=windows GOARCH=amd64 go build ./cmd/hack-browser-data/
# For Linux
GOOS=linux GOARCH=amd64 go build ./cmd/hack-browser-data/
Windows build with App-Bound Encryption (optional)
Chrome / Chrome Beta / Edge / Brave / CocCoc 127+ protect cookies with App-Bound Encryption. Decrypting those cookies requires a small C payload — Zig (0.13+) is the recommended C toolchain (the Makefile calls zig cc). MinGW-w64 gcc can also build the sources manually if you bypass make payload.
# 1. Install Zig
brew install zig # macOS
scoop install zig # Windows (scoop)
# or download from https://ziglang.org/download/
# 2. Build the payload (outputs internal/abe/payload/abe_extractor_amd64.bin)
make payload
# 3. Build hack-browser-data.exe with the ABE payload embedded
make build-windows
The resulting hack-browser-data.exe includes full ABE cookie decryption on Chromium 127+.
Usage
$ hack-browser-data -h
hack-browser-data decrypts and exports browser data from Chromium-based
browsers, Firefox, and Safari on Windows, macOS, and Linux.
GitHub: https://github.com/moonD4rk/HackBrowserData
Usage:
hack-browser-data [flags]
hack-browser-data [command]
Available Commands:
archive Pack decryption-relevant profile files into a zip for cross-host restore
dump Extract and decrypt browser data (default command)
dumpkeys Export Chromium master keys as JSON for cross-host decryption
help Help about any command
list List detected browsers and profiles
restore Decrypt copied profile data using exported master keys
version Print version information
Flags:
-b, --browser string target browser: all|chrome|firefox|edge|... (default "all")
-c, --category string data categories (comma-separated): all|password,cookie,... (default "all")
-d, --dir string output directory (default "results")
-f, --format string output format: csv|json|cookie-editor (default "json")
-h, --help help for hack-browser-data
--keychain-pw string macOS keychain password (visible in ps and shell history)
--keychain-pw-stdin read the macOS keychain password from the first line of stdin
-p, --profile-path string custom profile dir path, get with chrome://version
-v, --verbose enable debug logging
--zip compress output to zip
Use "hack-browser-data [command] --help" for more information about a command.
dump - Extract and decrypt browser data (default)
Running hack-browser-data without a subcommand defaults to dump.
Flag
Short
Default
Description
--browser
-b
all
Target browser (all|chrome|firefox|edge|...)
--category
-c
all
Data categories, comma-separated (all|password|cookie|bookmark|history|download|creditcard|extension|localstorage|sessionstorage)
--format
-f
json
Output format (csv|json|cookie-editor)
--dir
-d
results
Output directory
--profile-path
-p
Custom profile dir path, get with chrome://version
--keychain-pw
macOS keychain password (visible in ps and shell history)
--keychain-pw-stdin
Read the macOS keychain password from the first line of stdin
--zip
false
Compress output to zip
--format cookie-editor writes cookies as a JSON array matching the Cookie-Editor browser extension's import format; every other category is written exactly as the json format writes it.
Cross-host decryption
Decrypt browser data on an analyst host that was collected on a different origin host — including a browser whose engine the analyst's OS cannot even install (e.g. decrypt Sogou or QQ Browser data on macOS). Nothing platform-bound (DPAPI, macOS Keychain, Chrome App-Bound Encryption) has to leave the origin: the master keys are exported once, and decryption then runs entirely offline from a copy of the data.
The workflow uses three commands and two transportable artifacts:
Step
Host
Command
Produces
1
origin
dumpkeys
keys.json — portable master keys
2
origin
archive
browser-data.zip — only the files needed to decrypt
3
analyst
restore
decrypted output (csv / json / cookie-editor)
# On the origin host (any OS) — export the keys and pack the data
hack-browser-data dumpkeys -o keys.json
hack-browser-data archive -o browser-data.zip
# Copy keys.json + browser-data.zip to the analyst host, then decrypt offline
hack-browser-data restore --keys keys.json --data-zip browser-data.zip
keys.json contains plaintext master keys — treat it as a secret. dumpkeys -o writes it with 0600 permissions; prefer streaming it over a secure channel instead of leaving it on disk.
dumpkeys - Export master keys for cross-host decryption
Derives each Chromium installation's master keys on the origin host and writes them as JSON (Firefox / Safari have no portable key and are skipped). Defaults to stdout so it can be piped over SSH.
Flag
Short
Default
Description
--browser
-b
all
Target browser (all|chrome|edge|...)
--output
-o
stdout
Output file (written 0600); stdout if omitted
--keychain-pw
macOS keychain password (visible in ps / history)
--keychain-pw-stdin
Read the keychain password from stdin's first line
archive - Pack decryption-relevant files for transport
Collects only the files a restore actually needs (cookies, login data, history, …) through the same locked-file bypass used for extraction, so live SQLite files are read safely on Windows. The zip is laid out as <browser-key>/<User Data layout>, so one archive can carry several browsers and restore stays unambiguous. Entry names are always forward-slash, so a Windows-produced archive restores on macOS / Linux.
Flag
Short
Default
Description
--browser
-b
all
Target browser (all|chrome|edge|...)
--category
-c
all
Data categories, comma-separated
--output
-o
browser-data.zip
Output archive path
restore - Decrypt copied data with exported keys
Rebuilds each Chromium engine straight from keys.json and decrypts the supplied data — it never consults the analyst's local browser table, so the browsers you can restore are exactly the vaults in your keys.json. Supply the data one of two ways (exactly one is required):
--data-zip — a zip produced by archive; extracted to a temp dir and removed afterward.
--data-dir — a directory. Either the archive layout (<browser-key>/..., several browsers at once), or one browser's hand-copied User Data root, which is unambiguous only for a single browser — so pair it with -b.
-b is an optional filter over the dump's vaults, not a required selector.
Flag
Short
Default
Description
--keys
required
Keys file from dumpkeys (use - for stdin)
--data-zip
Zip from archive (mutually exclusive with --data-dir)
--data-dir
Copied data dir (mutually exclusive with --data-zip)
--browser
-b
Restore only this browser; must match a vault in --keys
--category
-c
all
Data categories, comma-separated
--format
-f
json
Output format (csv|json|cookie-editor)
--dir
-d
results
Output directory
--zip
false
Compress output to zip
Cross-host examples
# Stream keys over SSH (no keys.json on disk), data copied separately
ssh origin "hack-browser-data dumpkeys" | \
hack-browser-data restore --keys - --data-zip browser-data.zip
# Restore one browser from a hand-copied User Data folder (no archive)
hack-browser-data restore --keys keys.json --data-dir ./chrome-userdata -b chrome
list - List detected browsers and profiles
Flag
Default
Description
--detail
false
Show per-category entry counts
version - Print version information
hack-browser-data version
Global flags
Flag
Short
Description
--verbose
-v
Enable debug logging
Examples
# Extract all data from all browsers (default)
hack-browser-data
# Extract specific browser and categories
hack-browser-data dump -b chrome -c password,cookie
# Export in CSV format to a custom directory (JSON is the default)
hack-browser-data dump -b chrome -f csv -d output
# Export cookies in CookieEditor format
hack-browser-data dump -f cookie-editor
# Compress output to zip
hack-browser-data dump --zip
# List detected browsers and profiles
hack-browser-data list
# List with per-category entry counts
hack-browser-data list --detail
# Use custom profile path
hack-browser-data dump -b chrome -p "/path/to/User Data/Default"
Contributing
We welcome and appreciate any contributions made by the community (GitHub issues/pull requests, email feedback, etc.).
Please see the Contribution Guide before contributing.
Contributors
Roger
Aquilao Official
uinfziuna8n
slimwang
stevenlele
Cyrus
Carlo Mandelli
David Rogers
zznQ
YuXJ
mybonesaremorepowerful92
mirefly
LC
zhe6652
guoguangwu
freddy77
beichen
Santiago Ramirez
Daniel Uptain
Ciprian Conache
a-urth
Amir.
Stargazers over time
404StarLink 2.0 - Galaxy
HackBrowserData is a part of 404Team StarLink-Galaxy, if you have any questions about HackBrowserData or want to find a partner to communicate with, please refer to the Starlink group.
JetBrains OS licenses
HackBrowserData had been being developed with GoLand IDE under the free JetBrains Open Source license(s) granted by JetBrains s.r.o., hence I would like to express my thanks here.
moonD4rk/HackBrowserData thuộc nhóm Backend trên TopGit, cùng 16 topic GitHub. Trang Trending và Topics liệt kê các repo cùng số sao và cùng ngôn ngữ để so sánh.
Đọc thêm về moonD4rk/HackBrowserData ở đâu?
Trang TopGit này là một snapshot — tab "Readme" hiển thị nguyên văn README của repo (đã bỏ link, giữ ảnh). Repo GitHub ở github.com/moonD4rk/HackBrowserData là nguồn chính thức.
moonD4rk/HackBrowserData có bao nhiêu sao?
moonD4rk/HackBrowserData có 14.7k sao GitHub — tải lại trang để xem số mới nhất, hoặc xem trực tiếp github.com/moonD4rk/HackBrowserData. TopGit phản chiếu số sao của GitHub nhưng không cam kết đến từng phút.
moonD4rk/HackBrowserData có phải mã nguồn mở không?
Có — moonD4rk/HackBrowserData phát hành theo license MIT, nghĩa là mã nguồn mở để đọc, fork và (tùy license) tái sử dụng. Mã: github.com/moonD4rk/HackBrowserData.
moonD4rk/HackBrowserData có trang demo không?
Dự án có trang chủ ở https://hackbrowserdata.org. Tab "Readme" ở trang này thường có ảnh chụp và hướng dẫn bắt đầu nhanh.
moonD4rk/HackBrowserData là gì?
moonD4rk/HackBrowserData (moonD4rk/HackBrowserData) là dự án Go trên GitHub. Theo mô tả gốc: Decrypt and export passwords, cookies, history and more from 20 browsers on Windows, macOS and Linux. For authorized security research, incident response and DFIR.
moonD4rk/HackBrowserData so với các dự án Backend khác thế nào?
moonD4rk/HackBrowserData được TopGit xếp vào nhóm Backend, với 14.7k sao GitHub và viết bằng Go. Xem trang chủ đề Backend trên TopGit để so sánh với các dự án tương tự theo số sao và mức độ hoạt động.
Đọc đầy đủ README ở tab phía trên.
HackBrowserData có đáng để bạn bỏ thời gian?
ChatGPT, Claude và Perplexity đều đọc được trang này. Hỏi thử xem họ nghĩ gì về HackBrowserData.