Install bulk_extractor with Homebrew, MacPorts, Nix, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• bulk_extractor

Project history

bulk_extractor predates its current GitHub repository. The NEWS file includes 2010 release announcements for versions 0.4.2 through 0.7.0, with features such as context stop lists, compressed-data carving, crash protection, POSIX threading, ZIP/GZIP/PDF recovery, and hibernation-file extraction.

The `simsong/bulk_extractor` repository was created on 2012-04-03. The README describes the tool as a high-performance digital forensics exploitation tool that extracts email addresses, credit card numbers, JPEGs, JSON snippets, search terms, and other features, storing results in text files and histograms for inspection and downstream processing.

The README recommends citing Simson Garfinkel's 2013 Computers & Security paper, `Digital Media Triage with Bulk Data Analysis and bulk_extractor`, which formalized the technique and helped anchor the tool in academic and law-enforcement forensic practice.

Adoption history

Adoption came from forensic triage needs: investigators could run bulk_extractor against disk images or memory artifacts and quickly get feature files, histograms, and leads without mounting or interpreting the filesystem first.

The project also included BEViewer for inspecting output, documented production downloads through GitHub releases, and kept packaging-friendly build instructions for Unix-like systems. Package managers such as Homebrew, MacPorts, Nix, and openSUSE carry it because forensic analysts and security researchers often need repeatable installs on analysis workstations.

How it is used

Users point `bulk_extractor` at a disk image, file, directory, or other data source and review generated feature files and reports. It recursively examines decoded data, which lets it find artifacts in compressed, encoded, or carved content that simpler scanners miss.

The tool supports scanner selection, histograms, debugging environment variables, and VM-based build recipes. Modern 2.x development requires C++17 and uses submodules such as be13_api and DFXML.

Why package nerds care

bulk_extractor is significant because it packages a research-grade forensic idea into a normal CLI: scan every byte, extract features, and produce plain text output. That combination makes it useful both in investigations and in scripted security pipelines.

For package nerds, it is also a classic example of a domain-specific tool with deep native-code build requirements, academic provenance, GUI adjuncts, and long-lived release history that still belongs in general-purpose package managers.

Timeline

• 2010: 0.4.x through 0.7.0 release announcements document early stop-list, carving, threading, and crash-protection work.
• 2012: Public `simsong/bulk_extractor` GitHub repository is created.
• 2013: Computers & Security publishes the bulk data analysis and bulk_extractor paper cited by the project.
• 2024: 2.1.1 release notes document ongoing 2.x maintenance.
• 2026: The repository remains active as the development tree for current bulk_extractor work.

Related projects

• bulk_extractor is related to BEViewer, DFXML, be13_api, forensic carving tools, disk-image analysis workflows, memory and hibernation-file analysis, and downstream feature-file processing scripts.

Sources

• https://api.github.com/repos/simsong/bulk_extractor
• https://github.com/simsong/bulk_extractor#readme
• https://github.com/simsong/bulk_extractor/blob/main/NEWS
• https://github.com/simsong/bulk_extractor/wiki