Skip to main content

BLint

BLint is a Binary Linter that checks the security properties and capabilities of your executables. It is powered by lief. Since version 2, blint can also generate Software Bill-of-Materials (SBOM) for supported binaries.

BLint Demo

Supported binary formats:

  • Android (apk, aab)
  • ELF (GNU, musl)
  • PE (exe, dll)
  • Mach-O (x64, arm64)

You can run blint on Linux, Windows, and Mac against any of these binary formats.

Motivation

Nowadays, vendors distribute statically linked binaries produced by Golang, Rust, or Dotnet tooling. Users are used to running antivirus and anti-malware scans while using these binaries in their local devices. Blint augments these scans by listing the technical capabilities of a binary. For example, whether the binary could use network connections or can perform file system operations and so on. The binary is first parsed using the lief framework to identify the various properties, such as functions and the presence of symtab and dynamic symbols. Thanks to YAML-based annotation data, this information can be matched against capabilities and presented visually using a rich table. NOTE: The presence of capabilities doesn't imply that the binary always performs the operations. Use the output of this tool to get an idea about a binary. Also, this tool is not suitable for reviewing malware and other heavily obfuscated binaries for obvious reasons.

Use cases

  • Quickly identify malicious binaries by looking at their capabilities (Ability to manipulate networks or drivers or kernels etc)
  • Add blint to CI/CD to inspect the final binaries to ensure code signing or authenticode is applied correctly
  • Identify interesting functions and symbols for fuzzing

Installation

  • Install python 3.10, 3.11, or 3.12
pip install blint

Single binary releases

You can download single binary builds from the blint-bin releases. These executables should work without requiring python to be installed. The macOS .pkg file is signed with a valid developer account.

Usage

usage: blint [-h] [-i SRC_DIR_IMAGE [SRC_DIR_IMAGE ...]] [-o REPORTS_DIR] [--no-error] [--no-banner] [--no-reviews] [--suggest-fuzzable] [--use-blintdb] {sbom} ...

Binary linter and SBOM generator.

options:
  -h, --help            show this help message and exit
  -i, --src SRC_DIR_IMAGE [SRC_DIR_IMAGE ...]
                        Source directories, container images or binary files. Defaults to current directory.
  -o, --reports REPORTS_DIR
                        Reports directory. Defaults to reports.
  --no-error            Continue on error to prevent build from breaking.
  --no-banner           Do not display banner.
  --no-reviews          Do not perform method reviews.
  --suggest-fuzzable    Suggest functions and symbols for fuzzing based on a dictionary.
  --use-blintdb         Use blintdb for symbol resolution. Use environment variables: BLINTDB_IMAGE_URL, BLINTDB_HOME, and BLINTDB_REFRESH for customization.

sub-commands:
  Additional sub-commands

  {sbom}
    sbom                Command to generate SBOM for supported binaries.
    db                  Command to manage the pre-compiled database.

SBOM sub-command

usage: blint sbom [-h] [-i SRC_DIR_IMAGE [SRC_DIR_IMAGE ...]] [-o SBOM_OUTPUT] [--deep] [--stdout] [--exports-prefix EXPORTS_PREFIX [EXPORTS_PREFIX ...]]
                  [--bom-src SRC_DIR_BOMS [SRC_DIR_BOMS ...]]

options:
  -h, --help            show this help message and exit
  -i SRC_DIR_IMAGE [SRC_DIR_IMAGE ...], --src SRC_DIR_IMAGE [SRC_DIR_IMAGE ...]
                        Source directories, container images or binary files. Defaults to current directory.
  -o SBOM_OUTPUT, --output-file SBOM_OUTPUT
                        SBOM output file. Defaults to bom-post-build.cdx.json in current directory.
  --deep                Enable deep mode to collect more used symbols and modules aggressively. Slow operation.
  --stdout              Print the SBOM to stdout instead of a file.
  --exports-prefix EXPORTS_PREFIX [EXPORTS_PREFIX ...]
                        prefixes for the exports to be included in the SBOM.
  --bom-src SRC_DIR_BOMS [SRC_DIR_BOMS ...]
                        Directories containing pre-build and build BOMs. Use to improve the precision.

DB sub-command

usage: blint db [-h] [--download] [--image-url IMAGE_URL]

options:
  -h, --help            show this help message and exit
  --download            Download the pre-compiled database to the /Volumes/Work/blintdb/ directory. Use the environment variable `BLINTDB_HOME` to override.
  --image-url IMAGE_URL
                        Blintdb image url. Defaults to ghcr.io/appthreat/blintdb-vcpkg-arm64:v1. The environment variable `BLINTDB_IMAGE_URL` is an alternative way to set this value.

To test any binary, including default commands

blint -i /bin/netstat -o /tmp/blint

Use -i to check any other binary. For eg: to check ngrok

blint -i ~/ngrok -o /tmp/blint

Pass --suggest-fuzzable to get suggestions for fuzzing. A dictionary containing "common verbs" is used to identify these functions.

blint -i ~/ngrok -o /tmp/blint --suggest-fuzzable

To generate SBOM in CycloneDX format for supported binaries, use the sbom sub-command.

blint sbom -i /path/to/apk -o bom.json
blint sbom -i /directory/with/apk/aab -o bom.json

To parse all files, including .dex files, pass --deep argument.

blint sbom -i /path/to/apk -o bom.json --deep

Component identification for C/C++ binaries could be improved with blintdb. To download the pre-compiled database (SQLite format), first run the db command followed by the sbom command.

blint db
blint sbom -i /path/to/binary -o bom.json --deep

The following binaries are supported:

  • Android (apk/aab)
  • Dotnet executable binaries
  • Go binaries
  • Rust binaries
  • c/c++ binaries (WIP)
blint sbom -i /path/to/go-binaries -o bom.json --deep

For all other binaries, the symbols will be collected and represented as properties with internal prefixes for the parent component. Child components and dependencies would be missing.

PowerShell example

PowerShell

Reports

Blint produces the following json artifacts in the reports directory:

  • blint-output.html - HTML output from the console logs
  • exename-metadata.json - Raw metadata about the parsed binary. Includes symbols, functions, and signature information
  • findings.json - Contains information from the security properties audit. Useful for CI/CD integrations
  • reviews.json - Contains information from the capability reviews. Useful for further analysis
  • fuzzables.json - Contains a suggested list of methods for fuzzing

sbom command generates CycloneDX json.

References

Discord support

The developers can be reached via the Discord channel.

Sponsorship wishlist

If you love blint, you should consider donating to our project. In addition, consider donating to the below projects, which make blint possible.

Metadata

Release files for blint 2.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for blint 2.4.1
File Size Uploaded Provenance Actions
blint-2.4.1.tar.gz 147.5 kB With provenance Details for blint-2.4.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for blint 2.4.1
File Interpreter ABI Platform Actions
blint-2.4.1-py3-none-any.whl Python 3 none any Details for blint-2.4.1-py3-none-any.whl

Total release size: 306.7 kB

Release files / blint-2.4.1.tar.gz

Download URL blint-2.4.1.tar.gz
Size 147.5 kB
Tags Source
SHA-256 checksum
How to use checksums
98ea5e8b3c0d9d2a57df2b90809077eae8212edff8a97ec595a9728c036098ce
BLAKE2b-256 checksum
How to use checksums
2667facbccc0b6081de9bad9b7dfc938f87beeeb69a55472a7a3432c54c24537
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 3, 2025.

Transparency log

Release files / blint-2.4.1-py3-none-any.whl

Download URL blint-2.4.1-py3-none-any.whl
Size 159.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8f058a00868bdaa391e008981efc8ad7bf7c83f55c941997abe059ab47e387b8
BLAKE2b-256 checksum
How to use checksums
d180b7dc2cc3afe9f1bf0e805c26e3f54b02cc894643fc48b4f403e351471dba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 3, 2025.

Transparency log

Security for blint 2.4.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for blint-2.4.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 3, 2025.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

2.4.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page