Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
trailofbits/hunt-regressionsReverse engineering and fuzzing

hunt-regressions

⁨Use when discovering possible regressions from a pinned change and its callers before reproduction.⁩

v2026.11.12-149d7b23 installs+3 in 7 days8.2K StarsCC-BY-SA-4.0synced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install trailofbits/hunt-regressions

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
gn4tdrvCBs…g6AZS3CA==The CLI checks the SHA-256 and the signature before it writes a file.
Package97e1c235…9e24b115
97e1c2353ddd…e2d29e24b1151 file · ⁦1.1 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/trailofbits/skills/tree/main/plugins/regression-hunt/skills/hunt-regressions@149d7b2

When to Use

Input: sealed preparation, frozen S0/S1, change context and registry assignment. On retry, include this assignment's prior candidate-ID mapping. The caller supplies these, including for independent use. Follow project guidance before target work.

When NOT to Use

Proving a known candidate; use reproduction. Discovery cannot confirm findings.

Hunt

  1. Read the standard and file contract. Verify preparation; read frozen change messages, PR discussion and security documentation for intent and supported use.
  2. Review the entire diff; trace changed behavior through callers to real interfaces. Use frozen sources and supplied context, not later fixes, advisories or other reviews.
  3. Record each lead's changed code, previously supported behavior, reachable trigger, proposed new defect, false-positive checks and required proof. Retain supplied leads suggesting old bugs or incomplete fixes for adjudication. Leave PoC construction to reproduction.
  4. Reserve each lead's ID through registry.py candidate using its stable hypothesis key and assigned agent handle. Reuse the key on retry. Write candidate files and hunt.json with IDs, file mappings, coverage and limitations. An empty list is valid. If blocked, record partial coverage and uninspected areas. Seal the package.

Report Back

Keep detailed evidence in the sealed package. Return only:

  • Status: complete or blocked, matching the record.
  • Record: sealed hunt.json path, or why none was produced.
  • Result: candidate count and material coverage gaps.
  • Blocker: missing prerequisite or required caller action, if blocked.

Rationalizations to Reject

  • “A helper fails on invented input”: show a supported interface that reaches it.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.12-149d7b2Nov 13, 2026149d7b297e1c235Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login