Get-keys.bat

@echo off REM get-keys.bat REM Recursively search for likely keys/tokens in files and generate a CSV report. REM Usage: REM get-keys.bat [root_path] [--extensions=ext1,ext2,...] [--exclude=pattern1;pattern2] [--mask] [--dry-run] REM Defaults: REM root_path = current directory REM extensions = txt,env,conf,config,json,js,py,java,xml,ini,yml,yaml,md,log REM exclude = .git;.venv;node_modules;venv REM mask = redact found values in report REM dry-run = do not write report (only console output)

if "%DRY%"=="0" ( echo Report written to %OUTFILE% ) else ( echo Dry-run complete: no report written. )

set "OUTFILE=%CD%\get-keys_report_%DT%.csv" get-keys.bat

:: Write CSV header set "CSV_HDR=File,LineNumber,Context,MatchType,MatchValue" if "%DRY%"=="0" ( echo %CSV_HDR%> "%OUTFILE%" )

Below is a thorough, extensible Windows batch script named get-keys.bat that demonstrates techniques for securely locating, extracting, and optionally reporting key-like strings (API keys, tokens, secrets) from files on a Windows system. This is intended for legitimate use only — e.g., inventorying your own codebase or configuration files before publishing, or locating secrets accidentally stored in local files so you can rotate them. Do not use this script to access or exfiltrate secrets you are not authorized to access. @echo off REM get-keys

:: Timestamp for report for /f "tokens=1-6 delims=/:. " %%a in ("%date% %time%") do ( set "DT=%%a-%%b-%%c_%%d-%%e-%%f" ) if "%DT%"=="" ( REM fallback set "DT=%DATE%_%TIME%" set "DT=%DT::=-%" set "DT=%DT:/=-%" set "DT=%DT: =_%" set "DT=%DT:.=-%" )

setlocal ENABLEDELAYEDEXPANSION

:: -------------------------- :: Main scan loop :: -------------------------- pushd "%ROOT%" 2>nul || (echo Cannot access %ROOT% & exit /b 1)