Repository navigation
Release v4.0.0
blint 4.0 is the largest release in the project's history. Where v3 read binaries and reported hardening flags, v4 reads them the way a reverse engineer does: it walks the containers they arrive in, disassembles what matters, and reasons about behavior. Two full adversarial security reviews were run against this code before release, and every finding from both is fixed and covered by regression tests.
Reading more of what you actually ship
The default scan now understands the formats real installers and packages use. Windows coverage grew the most: MSIX and Appx packages including bundles with block map verification, MSI databases, CAB archives, ClickOnce manifests, NuGet packages, and 7z self extracting installers whose payload members are extracted and analyzed individually. Office documents are read for structure, macros and relationships, with .msg attachments becoming analyzable units of their own. On the Apple side, iOS and macOS bundles are walked end to end, including embedded frameworks, app extensions, host plugins, Swift metadata and provisioning profiles. WebAssembly support now emits SBOM components from Component Model interface packages.
Deeper analysis of every platform
Windows binaries get a .NET reader that understands strong name signatures, user string heaps and single file bundles, plus driver oriented passes for ioctl depth, kernel posture, PE catalogs, rich header toolchains and known vulnerable drivers. Android analysis handles split bundles, reviews dex bytecode with a dataflow pass, attributes JNI usage, and fingerprints native libraries. Where enabled with the disassemble flag, nyxstone backed disassembly feeds abstract interpretation, stack string recovery and call graph construction, and call graphs can be exported, fingerprinted and matched across builds with the new callgraph subcommands.
Faster and easier to run
A worker pool behind the jobs flag parallelizes scans across processes, including the frozen single file binaries that are now built for Linux, musl, Windows and both Mac architectures. A content addressed parse cache behind the cache flag makes repeated scans of unchanged bytes nearly free, and it is safe by construction: the cache key describes exactly the bytes that were parsed. SBOM generation can consult blintdb v2 for symbol and disassembly assisted component identification. There is also a stable Python API in blint.api, and new commands for capabilities, diffs, cache management and canonicalization. The CLI arguments and the JSON output shape from v3 keep working.
Security review before release
Because v4 added so much parsing of untrusted input, it was reviewed adversarially twice, exploit first. The fixes that came out of those reviews are part of this release. Archive member names can no longer escape the extraction directory in any format reader, and every extractor goes through one shared path safety gate. Decompression bombs are refused by per archive caps plus a cumulative budget that spans nested bundles. A shell is no longer involved in tool invocation on Windows, report tables escape untrusted names before rendering, and the HTML report initializes its diagram renderer in strict mode with a pinned version. The parse cache cannot be poisoned by a file that changes while it is being parsed, the blintdb image reference is validated before download, and untrusted XML is parsed with entity expansion forbidden throughout. The second review covered the analysis engines: the secret and banner detection regexes can no longer be stalled by crafted strings, the Mach-O signature parser has recursion depth limits instead of crashing on nested ASN.1, and the .NET metadata reader verifies declared table row counts against the bytes actually present. Resource ceilings now bound disassembly windows, section walks and profile reads. Each fix ships with a hostile fixture in the test suite.
Requirements
Python 3.10 through 3.14. Notable dependencies: lief 0.17.4 or newer, wasm-tools 2.1 or newer, defusedxml, apsw and oras. Users of the environment variables for the parse cache and blintdb will find them documented in the README, along with the new caps.
Full changelog: v3.4.0...v4.0.0