Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
nginx2root-ioc-scan — Looks for access-log behavior associated with CVE-2026-123007 HTTP/2 flow-control exploitation | Kitploit
Tools/GitHubGitHub/jenic/nginx2root-ioc-scan
Defensive ToolsIndicator of Compromise (IOC) ManagementVulnerability AnalysisWeb SecurityIncident ResponseLog Analysis
GitHubjenic/nginx2root-ioc-scan

nginx2root-ioc-scan

Looks for access-log behavior associated with CVE-2026-123007 HTTP/2 flow-control exploitation

View Repository
1 day agoNot yet reviewed
Share

nginx2root IOC scanner

This IOC scanner was written by OpenAI's Daybreak Blue.

nginx-ioc-scan looks for access-log behavior associated with CVE-2026-123007 HTTP/2 flow-control exploitation without relying on one client address or one request path. It detects:

  • aggregate bursts of HEAD requests;
  • aggregate bursts of oversized HEAD requests when request length is logged;
  • bursts of HTTP 206 Partial Content responses; and
  • a higher-confidence composite when HEAD and 206 bursts occur close together.

Build and test

The Makefile keeps Go build and module caches inside the repository:

make test
make build

Releases

Pushes and pull requests run the test suite, native builds, cross-platform release builds, release-automation tests, and a reproducibility check in GitHub Actions. Pushing a v-prefixed SemVer tag such as v1.2.3 automatically creates a GitHub Release after all CI checks pass.

Each release contains Linux and macOS archives for amd64 and arm64, Windows zip archives for amd64 and arm64, and SHA256SUMS. GitHub Actions also attaches a SLSA provenance bundle and keyless Sigstore bundles for every downloadable asset. Release archives can be built locally with:

make release-all VERSION=v1.2.3

Verify a downloaded archive against the checksum manifest with:

sha256sum --check --ignore-missing SHA256SUMS

The release page includes *.sigstore.json bundles for verification with Cosign and provenance.sigstore.json for verification with GitHub CLI.

Usage

Scan one or more logs, gzip archives, or standard input:

nginx-ioc-scan /var/log/nginx/access.log /var/log/nginx/access.log.1.gz
zcat /var/log/nginx/access.log.*.gz | nginx-ioc-scan
nginx-ioc-scan -output json -window 45s -head-count 30 access.json
nginx-ioc-scan -verbose /var/log/nginx/access.log*

Use -verbose to list the contributing filenames and rule-specific matching requests beneath each alert. Each match includes its source line, timestamp, request, response status, and request length when available. Verbose JSON adds structured sources and matches fields. Request details are capped at 100 per alert, with an omitted count reported when the cap is reached.

Exit status is 0 when no alerts are found, 1 when alerts are found, and 2 for invalid arguments or input failures. Thresholds are deliberately configurable; run nginx-ioc-scan -h for all options.

The stock combined format is enough to detect method and status bursts, but it does not contain request size. Add request length and connection context to make the strongest rule available:

log_format incident '$remote_addr - $remote_user [$time_local] '
                    '"$request" $status $body_bytes_sent '
                    '"$http_referer" "$http_user_agent" '
                    'request_length=$request_length request_time=$request_time '
                    'connection=$connection connection_requests=$connection_requests';

JSON logs are also accepted. Common nginx field names such as time_iso8601, remote_addr, request, request_method, request_uri, server_protocol, status, body_bytes_sent, and request_length are recognized. Client address and path cardinalities are reported as context only; detection thresholds apply across the complete log stream so distributed traffic is not split into harmless per-source groups. Records explicitly marked as HTTP/1.x or HTTP/3 are excluded; HTTP/2 records and records whose format omits the protocol are analyzed.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    593
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    371
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    336
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    326
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    322

Explore all tools

Browse our collection of tools

View all tools →