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
Tools/GitHubGitHub/rootsecdev/microburstsecretshunter
Defensive ToolsStatic AnalysisConfiguration AuditingCloud SecuritySecret DetectionMisconfigurationDatabase Security
GitHub
Share
rootsecdev/microburstsecretshunter

MicroburstSecretsHunter

Scans exported Azure domain dumps for plaintext passwords, connection strings, storage keys, and other secrets; generates redacted CSV/HTML reports for read-only audit workflows.

View Repository
2814626 days agoReviewed by Kitploit

MicroBurst Secrets Hunter

A PowerShell scanner that combs through MicroBurst Get-AzDomainInfo output for plaintext passwords, keys, connection strings, and other secrets that should never sit unencrypted in an Azure environment.

Built for read-only audit workflows: you collect a domain dump with MicroBurst (Reader access is enough for Get-AzDomainInfo), then point this tool at the output folder. It does not touch Azure itself — it only reads the files you already exported. Secret values are redacted in every report, so the output is safe to attach to findings.


Quick start

# Clone / copy this folder, then from a PowerShell prompt:
.\Scan-MicroBurst.ps1 -Path .\MicroBurst-2026 -Verbose

Or import the module and use the cmdlet directly:

Import-Module .\MicroBurstSecretsHunter.psd1 -Force
Invoke-MBSecretScan -Path .\MicroBurst-2026

Reports are written to a timestamped folder (MBSecretScan-<timestamp>) in the current directory unless you pass -OutputDirectory.

By default every value is redacted so the reports are safe to share. The revealed characters are budgeted at a quarter of the value's length (capped at 4 leading + 2 trailing), and anything 8 characters or shorter is replaced with a fixed-width mask — so a typical password shows as ********, while an 88-char storage key stays identifiable as AAAA**********AA. Context strings are redacted before they are truncated, and every secret found on a line is redacted out of every finding's context on that line, so no plaintext survives in a report. When triaging false positives it's often faster to see the full value — pass -ShowSecrets to emit unredacted values everywhere (console, CSV, HTML, JSON, SARIF). The console and HTML then carry a clear warning banner, and the reports must be treated as live credential material:

Invoke-MBSecretScan -Path .\dump -ShowSecrets        # raw values, for local triage

Works on PowerShell 7+ (Windows, Linux, macOS).


What you get

Every run produces:

OutputDescription
Console summaryColor-coded counts by severity/category plus the top Critical/High findings.
findings.csvOne row per finding (severity, rule, file, line, redacted value, context) for triage in Excel. Fields carrying scanned content are escaped against spreadsheet formula injection.
report.htmlSelf-contained HTML report (no external assets, locked down by a Content-Security-Policy) with severity cards, live text filter, and severity toggles — shareable with the client.
findings.jsonScan metadata plus every finding, for scripting and tooling (-NoJson to skip).
findings.sarifOptional SARIF 2.1.0 log for code-scanning tools (-Sarif).

Each output folder also gets a small .mbsecretscan-output marker file so a later scan whose root contains it skips it (see Coverage limits).

The cmdlet also emits finding objects to the pipeline, so you can post-process:

$f = Invoke-MBSecretScan -Path .\dump -Quiet
$f | Where-Object Severity -eq 'Critical' | Format-Table File,Line,RuleName

What it detects

RuleSeverityExample source in a dump
SQL/DB connection string with embedded passwordCriticalApp Service settings, web.config exports
Azure Storage account connection string / 88-char keyCriticalApp settings, Storage exports
Service Bus / Event Hub SharedAccessKeyCriticalMessaging resource configs
Cosmos DB account keyCriticalApp settings
PEM private key blockCriticalKey Vault / certificate exports
Azure Function key (?code= in a Function / Logic App URL, x-functions-key)HighLogic App definitions, app settings
ARM parameter value ("adminPassword": { "value": "..." }, including pretty-printed across lines)HighARM templates / parameter files
Azure Redis Cache passwordHighCache connection strings
Azure AD client secret (post-2021 …Q~… format)HighARM templates, app settings
SAS token / sig= parameterHighStorage SAS URLs
JWT / bearer tokenHighCached tokens, configs
Certificate / key file present (.pfx, .p12, .pem, .key, .jks, .ppk, …)HighAnywhere in the dump
Certificate file present (.cer, .crt, .der — usually public)LowAnywhere in the dump
Generic password / pwd assignment, including compound names (administratorLoginPassword, userPWD)HighAutomation variables, app settings, ARM params, publish profiles
Generic secret / client_secret assignment, including compound names (servicePrincipalSecret)HighApp settings, templates
AWS access key / GitHub / Slack tokensHigh/MedForeign creds stored in Azure apps
Generic api_key / access_key / connectionstringMediumApp settings
High-entropy string (heuristic)LowBackstop for unknown key formats — opt-in via -IncludeEntropy

The generic keyword rules match the keyword at the end of a compound name (sqlAdminPassword, servicePrincipalSecret, storageAccountKey), so metadata fields that merely start with one (passwordLastSet, secretName) stay quiet. A generic value stops before whitespace followed by another key=/key:, so password=abc apikey=xyz yields two clean findings, while a passphrase containing spaces is still captured whole.

One finding per secret. When several rules match the same value on the same line (a storage connection string and the bare 88-char key; a SQL connection string and the generic password rule), only the highest-severity match is kept. On a tie, a format-specific rule (AZ_AAD_CLIENT_SECRET) wins over a keyword-driven one (GENERIC_*, ARM_PARAM_*, CSV_*).

The full, editable rule set lives in Private/Get-MBSignature.ps1. Each rule is a [PSCustomObject] with these fields:

FieldRequiredPurpose
Id, Name, Category, SeverityyesIdentity and how the finding is reported and sorted.
PatternyesThe regex. Compiled once per scan.
ValueGroupyesWhich capture group holds the secret (0 = whole match). Drives redaction.
MultiLinenoEvaluate against whole-file text instead of line by line (PEM blocks, pretty-printed ARM parameters). Every match is reported, not just the first, on the line where ValueGroup starts.
CaseSensitivenoOpt out of the default IgnoreCase compilation. Set this for formats defined case-sensitively (AKIA, ghp_, eyJ, Q~) — without it, arbitrary-case lookalikes match.
RedactnoSet $false when the captured value is a label rather than a secret (a PEM header line, a certificate file name) so it appears verbatim instead of masked into unreadability. Defaults to redacting.

Structured CSV column-pairing

Get-AzDomainInfo exports automation-account variables and app settings as Name,Value[,Encrypted] rows. The secret lives in the Value column while the keyword that identifies it (e.g. ServiceAccountPwd, dbConnectionString) lives in the Name column — so a plain regex never sees them on the same "line" and the keyword is buried inside a compound token with no word boundary.

For .csv / .tsv files the scanner additionally does structured column pairing (Private/Get-MBCsvFinding.ps1):

  • Name/Value mode — classifies each row's Name cell; if it's sensitive and the Value cell holds real data, it's reported. Rows marked Encrypted=True are skipped (the value is not plaintext).
  • Sensitive-column mode — if a column header is itself sensitive (a Password or StorageKey column), every non-placeholder cell is reported.
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →