HackNotice icon

HackNotice

Call the HackNotice extensions API (alerts, assessments, and more)

Actions85

Leak File Search → Count

AI-generated

Summary

Count HackNotice leak files matching a filename term, a word pool, or filters alone. Use the returned count and calculated page count to plan subsequent searches.

Inputs

  • leakFileSearchMode — Choose Term (default), Word Pool, or Filters Only. Filters Only sends the additional filters and time constraints without adding a term or word pool.
  • leakFileTerm (required) — Required in Term mode: a nonblank phrase to match against leak file names. Leading and trailing whitespace is removed.
  • leakFileSearchType — In Term mode, choose match_phrase (default), wildcard_both, wildcard_post, or wildcard_pre.
  • leakFilePool (required) — Required in Word Pool mode: a JSON array containing at least one nonblank search term, such as ["combo", "database"].
  • leakFilePoolSearchTypes — Optional JSON array of per-term search types in Word Pool mode, such as match_phrase, wildcard_post, wildcard_pre, or wildcard_both. An empty array adds no searchtype field.
  • leakFileMatch — Minimum number of word-pool terms that must match; defaults to 1. Must be at least 1 and is rounded down to an integer.
  • leakFileTimeRange — Optionally filter by timestamp using a custom range or the last day, week, or month. Relative windows start at local midnight one day, seven days, or one calendar month ago. None (default) preserves date filters supplied in Additional Filters; other choices replace startdate, enddate, and hours_ago.
  • leakFileStartDate (required) — Required for a custom time range: a valid start date, sent as YYYY-MM-DD using the runtime's local timezone.
  • leakFileEndDate (required) — Required for a custom time range: a valid end date, sent as YYYY-MM-DD using the runtime's local timezone.
  • leakFileAdditionalFilters — Optional JSON object of filters, such as domain, tag, tags, taggroup, password_type, severity, min_size, max_size, min_linecount, max_linecount, process_startdate, or process_enddate. Selected search parameters and time constraints overwrite corresponding fields.

Output shape

One JSON record per input item containing count, pageSize, and pageCount.

Posts to /leakfilesearch/count. pageSize is always 50 and pageCount is ceil(count / 50); no leak file records are returned. The node accepts a numeric response or a count/total field, including numeric strings, and defaults count to 0 if no numeric count can be extracted.

Links

Discussion