Updated Jul 14, 2026

Recon

Pull app-linked hosts without holding the APK

CLI client for the BeVigil OSINT API, keyed by domain or app package.

Agent

overview

What bevigil does

bevigil queries the BeVigil OSINT API, a dataset built by indexing mobile apps. Start from --domain for subdomains and urls, or from --package for hosts, params, s3, and wordlist. That surfaces infrastructure domain-only recon often misses.

Asset-type selects the lookup. Pair it with --domain, --package, --subdomain, or --keyword as the type requires. Every request needs a BeVigil API key supplied as a file input.

Wire subdomains and URLs into httpx, or S3 names into a bucket scanner. The managed recon node takes the API key file plus --domain or --package and writes a file and a folder of results.

source github.com/Bevigil/BeVigil-OSINT-CLI

use cases

Where bevigil fits

Pull subdomains and URLs for a domain

Query the subdomains or urls asset type for a domain to add app-sourced names and endpoints to a recon dataset that passive crawlers miss.

Recon a mobile app's backend

Look up hosts, parameters, and S3 buckets for an app package to map the infrastructure that mobile app talks to.

Find app-linked S3 buckets

Request the s3 asset type by keyword or package to surface storage buckets tied to the target, then hand them to a bucket scanner.

Seed parameter and wordlist discovery

Pull params and wordlist asset types for a package to seed fuzzing and parameter-discovery stages with target-specific values.

reference

bevigil inputs and flags

6 inputs
NameTypeFlagDescription
asset-typeSTRING·Asset type: hosts, packages, params, s3, subdomains, urls, or wordlist.
domainSTRING--domainDomain to query (asset-type packages, subdomains, or urls).
packageSTRING--packageApp package to request hosts for (asset-type host, params, s3, or wordlist).
subdomainSTRING--subdomainSubdomain to query (asset-type packages).
keywordSTRING--keywordKeyword to request S3 bucket info for (asset-type s3).
api_keyFILE·BeVigil API key file that authorizes the requests.

Showing key inputs. bevigil exposes 6 inputs in total.

example

Run bevigil

bevigil · command
# app-sourced subdomains for a domainbevigil subdomains --domain example.com # S3 buckets tied to a keywordbevigil s3 --keyword example
sample output
[*] Requesting subdomains for example.com from the BeVigil OSINT API api.example.comassets.example.comm.example.comstaging.example.comvpn.example.com [*] 5 subdomains written to bevigil/subdomains.txt

guidance

Choosing bevigil

Use bevigil when you need app-sourced OSINT (subdomains, URLs, buckets, params) that domain-only tools miss. It requires a BeVigil API key. For passive subdomains without that API, use subfinder.

subfinder

Passive subdomain discovery across many free sources. bevigil adds the mobile-app angle behind an API key.

bbot

Modular OSINT engine that chains many sources. bevigil is a focused client for one rich dataset.

apkurlgrep

Pulls URLs from an APK on disk. Local sibling to bevigil's app-sourced URL data.

faq

bevigil questions

Supply the BeVigil API key as a file input on the node. For local CLI use, run bevigil init or set BEVIGIL_API_KEY. Every asset-type request counts against that key's quota.

Run bevigil yourself

A domain feeds bevigil, which pulls app-sourced subdomains and URLs from the BeVigil API and passes them to httpx so only the live ones land as output.

Facts on this page come from the live Trickest tool library.