Skip to content
KitploitKITPLOIT
ИнструментыБлог
Log in
Отправить
ИнструментыБлог
Отправить

Инструменты для хакинга, пентеста и кибербезопасности — ваш арсенал защиты!

Kitploit — это каталог инструментов для хакинга, кибербезопасности и пентестинга. Находите последние обновления проектов для поиска уязвимостей, анализа систем, автоматизации тестирования и усиления вашей безопасности.

ЛентыКонтактыКонфиденциальность© 2026 Kitploit

Каталог инструментов

Категории

Все категории
Loading categories
sif — the blazing-fast pentesting suite. | Kitploit
Инструменты/GitHubGitHub/vmfunc/sif
ReconnaissanceVulnerability ScannersPort ScanningExploitationInformation GatheringWeb SecurityPenetration TestingSubdomain EnumerationCrawlerDNS Analysis
GitHubvmfunc/sif

sif

the blazing-fast pentesting suite.

Репозиторий
614275010 дней назадПроверено Kitploit
Поделиться
Контент недоступен на запрошенном языке. Показываем английскую версию.
sif



go version build license aur nixpkgs homebrew apt discord

install · picker · usage · modules · docs · contribute

fast, concurrent recon to exploitation in one binary. every scanner shares one connection-pooled http client.


what is sif?

sif is a recon and exploitation scanner that runs the whole chain in one binary: subdomain enum, port scan, crawler, nuclei, framework/cve detection, js secret extraction, web-vuln probes (cors/xss/redirect), cloud and takeover checks. 25+ scan types, one command.

sif -u https://example.com -dnslist -ports -crawl -js -framework -nuclei

nuclei and colly are compiled in as libraries rather than shelled out to (there's no exec.Command in the tree), so it's a single static binary with no runtime dependencies and nothing to wire together.

every scanner runs through one shared http client and a work-stealing worker pool. -proxy, -H, -cookie and -rate-limit apply to the whole run at once, connections get pooled and reused across the scan (a single-host run reuses one connection for ~50 requests instead of dialing 50 times), and a slow host doesn't hold the rest up. that shared client is the practical reason to use it over piping a stack of separate tools together. port scanning is connect()-based, so rustscan and nmap are still faster at raw port scans.

it reads targets from stdin and prints findings one per line under -silent, so it composes:

subfinder -d example.com | sif -silent -crawl -js -nuclei | notify

-diff turns a re-scan into a monitor that only reports what changed, -notify posts to slack/discord/telegram/webhook, and runs export to sarif and markdown.

install

homebrew (macos)

brew tap vmfunc/sif
brew install sif

arch linux (aur)

install using your preferred aur helper:

yay -S sif
# or
paru -S sif

nix

# nixpkgs (declarative: add to configuration.nix or home-manager)
environment.systemPackages = [ pkgs.sif ];

# or imperatively
nix profile install nixpkgs#sif

# or just run it without installing
nix run nixpkgs#sif -- -u https://example.com -headers -sh -framework

the repo also ships a flake if you want to build from source:

nix run github:vmfunc/sif

debian/ubuntu (apt)

curl -1sLf 'https://dl.cloudsmith.io/public/sif/deb/setup.deb.sh' | sudo -E bash
sudo apt-get install sif

from releases

grab the latest binary from releases.

from source

git clone https://github.com/vmfunc/sif.git
cd sif
make

requires go 1.26+

aur (manual install)

git clone https://aur.archlinux.org/sif.git
cd sif
makepkg -si

interactive picker

new to sif? just give it a target and pick what to run from a menu — no need to know the flags:

./sif https://example.com

with no scan flags on a terminal, sif opens an interactive picker: a grouped checklist of scans (recon, web vulns, info, intel), each showing its flag and a one-line description, with presets (quick, recon, web, full, passive) on p and a live "equivalent command" line so you can graduate to flags. your last selection is remembered.

it stays out of pipelines: any scan flag present runs directly, and -silent/-api/piped stdin or stdout never open it. force it on with -i (or -pick), off with -no-tui.

scans on an interactive terminal run under a live dashboard that streams findings as they land and ends on a browsable summary (j/k to move, enter for detail, w to write a report). anything non-interactive gets the plain streaming output, and -no-tui turns the dashboard off. see docs/tui.md for the full keybindings.

usage

# interactive picker: pick scans from a menu
./sif https://example.com

# basic scan
./sif -u https://example.com

# directory fuzzing
./sif -u https://example.com -dirlist medium

# subdomain enumeration
./sif -u https://example.com -dnslist medium

# port scanning
./sif -u https://example.com -ports common

# javascript framework detection + cloud misconfig
./sif -u https://example.com -js -c3

# shodan host intelligence (requires SHODAN_API_KEY env var)
./sif -u https://example.com -shodan

# securitytrails domain discovery (requires SECURITYTRAILS_API_KEY env var)
# discovers subdomains + associated domains, then scans all of them
./sif -u https://example.com -securitytrails -headers

# sql recon + lfi scanning
./sif -u https://example.com -sql -lfi

# web vuln probes (cors, open redirect, reflected xss)
./sif -u https://example.com -cors -redirect -xss

# framework detection (with cve lookup)
./sif -u https://example.com -framework

# a broad sweep
./sif -u https://example.com -dirlist small -dnslist small -ports common -headers -sh -cms -framework -git -whois

run ./sif -h for all options.

commands

a couple of subcommands run without scanning:

# print the version (release builds are stamped; local builds use git describe)
./sif version

# show the latest release notes (also -pn)
./sif patchnote

# validate every module (schema, matchers, regex, duplicate ids)
./sif modules lint

# run modules' inline test fixtures
./sif modules test

the first time you run a new release, sif prints that release's notes once. set SIF_NO_PATCHNOTES=1 to turn that off.

sif modules lint and sif modules test take optional file or directory paths; with none they cover the built-in and user module directories. both exit non-zero on failure, so they drop straight into CI. see docs/modules.md for details and the test-fixture format.

modules

sif has a modular architecture. modules are defined in yaml and can be extended by users.

built-in scan flags

Скачать инструмент

Популярное

Смотреть все →

Откройте для себя самые используемые инструменты нашего сообщества.

Данных о популярности пока нет.

Изучить все инструменты

Просмотрите нашу коллекцию инструментов

Смотреть все инструменты →