dpapi-toolkit - one tool for almost any Windows DPAPI blob
https://t.co/jllMmMRSzx
If you've done red teaming or pentesting long enough, you know how much of Windows comes down to DPAPI blobs - credentials, certificates, configs, browsers, Wi-Fi, RDP, the lot. The real work is knowing exactly what is encrypted, where it lives, and how to unwrap it: which master key a given blob needs, and what type of blob you're even looking at.
I've always loved mimikatz - one of the first tools to bring DPAPI decryption to so many formats. But as you know, you have to be sure which format you're decrypting, and if you pick wrong, the parser just crashes.
So I wanted one tool that makes any DPAPI-encrypted blob just work: drop the blob, it tells you which master key it needs, drop that too, set the SID/PVK/SYSTEM-key, get the result. It also exports DPAPImk/MSONLINEACCOUNT hashes for offline password cracking, plus a lot of other functions - and it's built as a Web GUI with drag-and-drop and intuitive, step-based actions.
Fully offline - you bring the collected files. Built for red team / pentest and DFIR, and research.
If you love playing with DPAPI as much as I do, please give it a try!
@PumpkinSecurity Yeah, separate. Pre-Windows 2000 Compatible Access is the ACL that makes the null session work. SAMR monitoring is whether they see you use the pipe to pull the data.
On red team engagements we often may start from a dropbox on the internal network (LAN/Wi-Fi) with no valid domain account. The DCs are easy to find via DNS, and still in plenty of environments anonymous access to the SAMR and LSARPC named pipes are open.
https://t.co/e94x09tKOi
Many of us lean on rpcclient for this (I do too), but over a null session it lists standard users by name only — no machine ($) accounts, full detail one queryuser at a time, and no way to RID-cycle when enumeration is locked down. enum4linux-ng and NetExec cover this ground too and I still use them. I wanted one command that does the whole pass and writes clean, reusable output:
• Users with full detail — descriptions, account restrictions, group memberships
• Groups resolved to their members
• Computer ($) accounts — via RID cycling, which is how you get them at all
• Domain + password/lockout policy, plus LSA/DNS (domain SID, forest, trusts)
• "Interesting" accounts flagged
Output is txt/csv/json plus ready-to-use lists: usernames for AS-REP roasting, computer names for the pre-Windows 2000 machine-account check. SAMR first; if that's locked it still returns LSA recon, with an optional LSA RID-cycling fallback.
Use it only on directories you are authorised to inspect.
@PumpkinSecurity Standing check only if we have no foothold - we don’t run it first if we already have a user. If SAMR isn’t logged well it can still be the quieter way to pull users/groups. Otherwise it shows up at the end as a mitigation note.
@PumpkinSecurity Yeah, I've seen it on the newer DCs too. To be fair, it's a legacy issue in terms of how the misconfiguration gets there. It mostly happens due to GPO migration and having Anonymous logon and Everyone present in the 'Pre-Windows 2000 Compatible Access' group.
One more to go: adexview - browse, search and audit an AD Explorer snapshot offline, in your browser, from any OS.
https://t.co/YlSMMD0mtA
Every engagement I had a .dat file and questions BloodHound doesn't answer: subnets, DNS name to IP, DFS shares, GPO links, LAPS coverage, certificate templates, trusts. AD Explorer knows, one object at a time, on Windows only.
So I built adexview on top of adx-query by @takito1812, whose offline LDAP engine for snapshots proved the whole idea. Thank you, Víctor.
What you get:
- directory tree, every attribute decoded (ACLs, DNS, certs, flags)
- LDAP filters and full-text search over the whole snapshot
- an audit with findings: dangerous ACLs, DCSync, RBCD, ESC1-5, LAPS, trusts
- a multi-snapshot library with upload and convert
- password login by default
Pairs with adexsnap for taking the snapshot from Linux or macOS.
AD Explorer snapshots without Windows.
https://t.co/1QOuc9rwBe
adexsnap is a Python CLI that talks LDAP from Linux or macOS and writes a real AD Explorer .dat file. Open it in AD Explorer, feed it to https://t.co/uj0O5nfBCU or BOFHound, ingest into BloodHound.
NTLM, Kerberos (ccache/kirbi), LDAPS. Built-in verifier.
Authorized use only. Hope it will be useful.