Automic VaultAutomic Vault

brew

hack-browser-data mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für hack-browser-data in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install hack-browser-data

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Command-line tool for decrypting and exporting browser data

Befehle und Aliase

  • hack-browser-data

Verlauf

Projektgeschichte und Nutzung

HackBrowserData is a Go command-line security and forensics tool for decrypting and exporting browser data. Its package identity is straightforward: install one binary, point it at local browser profiles or archived profile data, and export passwords, cookies, history, bookmarks, downloads, storage, extensions, and related browser artifacts.

Projektgeschichte

The public GitHub repository was created in June 2020. The README describes support for Chromium-based browsers and Firefox on Windows, macOS, and Linux, plus Safari on macOS, and includes a legal-use disclaimer aimed at security research.

The project evolved from local extraction into richer workflows. Release notes and README content show additions such as local storage export, pure-Go SQLite-related refactoring, optimized encryption/decryption modules, Safari support, Chromium App-Bound Encryption support, and cross-host decryption workflows.

Adoptionsgeschichte

Adoption is visible in the repository scale, release activity, and packaging through Homebrew. The tool appeals to incident-response, red-team, browser-forensics, and security-lab users because browser secrets and artifacts are spread across OS-specific stores, SQLite databases, browser profile layouts, keychains, and DPAPI-like mechanisms.

Cross-host decryption broadened its operational model: an origin host can export Chromium master keys and archive relevant profile files, while an analyst host restores and decrypts offline, even across operating systems for some browser families.

Wie es verwendet wird

The default `dump` command extracts local browser data with flags for browser, category, output directory, format, profile path, macOS keychain password, verbosity, and zip output. Other commands list profiles, export master keys, archive decryption-relevant files, restore copied profile data with exported keys, and print version information.

Supported data categories include passwords, cookies, bookmarks, history, downloads, credit cards for Chromium-based browsers, extensions, localStorage, and sessionStorage where supported. The README notes platform-specific requirements such as Full Disk Access for Safari and extra payload support for some Chromium cookie decryption on Windows.

Warum Paket-Nerds sich dafür interessieren

HackBrowserData is notable as a packaged security tool because it compresses many browser- and OS-specific storage rules into one CLI. For package users, the value is less about a library API and more about repeatable collection, export formats, cross-platform builds, and workflows that can be scripted during authorized investigations.

Zeitleiste

  • 2020: Public repository created.
  • 2022: v0.4.x releases included browser-data extraction fixes and local-storage support.
  • 2024: v0.4.6 release notes described refactors, pure-Go driver work, and encryption/decryption optimization.
  • 2026: v1.x release notes documented architecture rewrite, Safari, Chromium App-Bound Encryption, and cross-host decryption and restore workflows.

Related projects

  • Related surfaces include Chromium, Chrome, Edge, Brave, Firefox, Safari, browser profile SQLite databases, Windows DPAPI and App-Bound Encryption, macOS Keychain, and incident-response tooling that inventories browser artifacts.

Sicherheitslage

Risikostufe: blue

broad file, network, media, or database tool signal.

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

  • broad file, network, media, or database tool signal

Signale

  • text:decrypt

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
hack-browser-datacliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version1.1.0
Manager aktualisiert2026-06-14
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.1.0

https://github.com/moonD4rk/HackBrowserData

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:hack-browser-data
Version1.1.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/hack-browser-data
Homepagehttps://github.com/moonD4rk/HackBrowserData
Repositoryhttps://github.com/moonD4rk/HackBrowserData
Upstream-Dokumentationhttps://github.com/moonD4rk/HackBrowserData#readme
LizenzMIT
Quellarchivhttps://github.com/moonD4rk/HackBrowserData/archive/refs/tags/v1.1.0.tar.gz
Zuletzt aktualisiert2026-06-14T12:11:17Z
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namehack-browser-data
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment