They contained the host. I still had the network.
My CODE BLUE 2026 talk "Pass-the-Device" is now public: slides (EN/JA), 5 recon tools, experimental Sigma + KQL detections.
github.com/crypt0p3g/pass-th…
The idea: device trust is not device binding.
From one compromised, enrolled laptop there are two routes off the host:
A) copy existing state: cert, cookie, client config
B) enroll a new client with the user's SSO
Both end on a machine with no EDR. Each leaves a different record to revoke.
The goal is practical: to know where the trust boundaries are, to know the limits of what your VPN/SASE solution can do, and to understand which configuration you need.
Two real cases, Cisco and Zscaler: host isolated, account disabled, and the second session stayed alive. A fresh VPN/SASE enrollment is persistence outside EDR.
Three checks for defenders this week:
1. Do your VPN/SASE, enrollment and IdP logs reach the SIEM at all?
2. Compare every device enrolled in the last 90 days with your managed-device inventory.
3. Add one line to the IR playbook: end the user's VPN/SASE sessions and revoke the enrollments, not only the host.
Thank you @codeblue_jp.
#codeblue_jp#codeblue2026
dpapi-toolkit - one tool for almost any Windows DPAPI blob
github.com/crypt0p3g/dpapi-t…
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!
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.
github.com/crypt0p3g/adnulle…
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.
One more to go: adexview - browse, search and audit an AD Explorer snapshot offline, in your browser, from any OS.
github.com/crypt0p3g/adexvie…
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.
github.com/crypt0p3g/adexsna…
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 ADExplorerSnapshot.py or BOFHound, ingest into BloodHound.
NTLM, Kerberos (ccache/kirbi), LDAPS. Built-in verifier.
Authorized use only. Hope it will be useful.
今まで基本的に招待で登壇させていただいていたのですが、今年初めてCFPを出してみようと思い、とても嬉しいことにCODE BLUE 2026に採択されました。多くの場合、十分にリスクとして認識されていない、長年使ってきたテクニック—端末侵害後の活動の一部でもある「信頼の移植(Pass-the-Device)」についてお話しできればと思います。ペンテスト/Red Teamの方々には永続化や攻撃範囲を広げるネタとして、防御側の方々にはリスクの認知と対策・監視の観点で知ってもらいたいです。
#codeblue_jp#codeblue2026codeblue.jp/program/time-tab…