Independent offensive security research

Offensive security,reconstructed from evidence.

Advanced pentest field notes and independent CVE analysis across web, identity, mobile, and wireless systems. Clear conditions, visible evidence, defensible impact.

46Field notes
4Published CVEs
13+Years in security
Latest casefileCVE-2025-32463public sources reviewed
Calibrating a Root-Namespace Load DetectorAug 30, 2026 · 9 min readOpen analysis
Selected research

Five systems. Five evidence-led casefiles.

Chosen for original evidence, negative controls, reproducible method, and surface diversity—not recency or publishing volume.

Browse by topic →
01Web

The Flow Is Standard. The Bypass Is in the Half You Skipped.

OAuth 2.0 and OIDC vulnerabilities are almost never in the specification. They are in the parts implementations leave out — state, PKCE, exact redirect matching, audience validation — and the flow runs perfectly while each omission sits there waiting.

8 min readOpen casefile ↗
02Mobile

Android App Links: The Link Was Verified. The Action Was Not.

A field methodology for Android App Links that separates domain ownership, route validation, application state, and server-side authorization before calling a deep link secure.

18 min readOpen casefile ↗
03Wireless

The Handshake Was Captured. The Network Was Not.

A Wi-Fi assessment methodology that separates radio visibility, network identity, authentication, client trust, and post-association access before calling a wireless test successful.

18 min readOpen casefile ↗
04Identity

BloodHound Path Triage: The Shortest Path Is Usually the One That Expires First

BloodHound draws every edge the same width, but a DACL lasts for years and a session lasts for minutes. Shortest-path queries are biased toward exactly the edges least likely to still be there when you walk them.

7 min readOpen casefile ↗
05CVE research

CVE-2025-32463: How a User-Controlled Chroot Loaded Code as Root

A reader-first root-cause analysis of CVE-2025-32463: how sudo entered an attacker-controlled filesystem before authorization completed, why NSS could then load a library as root, and what 1.9.17p1 changed.

11 min readOpen casefile ↗
Personal research

Responsible Disclosures

Firms contacted through authorized reporting channels during personal security research. No endorsement, employment, or client relationship is implied.

gdb — crash triageOpen transcript
$ gdb -q ./authd --core core.4412

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000401e6c in parse_session_hdr (h=0x7ffd9c40) at session.c:214
214         memcpy(ctx->token, h->token, h->token_len);

rip 0x0000000000401e6c   rsp 0x00007ffd9c40
rax 0x4141414141414141   rdi 0x00000000004052c0

$ checksec --file=./authd
RELRO Partial   Canary absent   NX enabled   PIE no

[+] token_len unbounded — 72 bytes reach saved RIP
[+] no canary, no PIE — control transfer is one gadget away
Evidence, not theatre

A finding should survive the handoff.

The useful part is not the screenshot. It is the chain from observable behavior to root cause, bounded impact, and a fix the receiving team can verify independently.

  • 01 Reproduction with stated preconditions
  • 02 Negative controls and exploitability boundaries
  • 03 Defender-ready remediation and retest criteria
See the public research pipeline →
Research lanes

Three areas, one standard.

Each note carries the same burden of proof: reproducible steps, stated preconditions, demonstrated impact.

01

Web application attacks

Authentication bypasses, business logic flaws, API attack paths, and client-side validation gaps — tested with reproducible steps.

Auth · APIs · business logic
02

Vulnerability research

Root-cause analysis, variant hunting, exploitability boundaries, and patch diffing from authorized engagements.

Root cause · variants · exploitability
03

Attack surface analysis

Asset discovery, cloud misconfiguration chains, identity paths, and external attack surface enumeration at scale.

Cloud · identity · external surface
Latest

Write-ups

Full write-ups: how the bug was found, why it works, and what it takes to trigger it.

View all →
Guided reading

Complete series

Start at part one and follow one problem from first signal to defensible conclusion.

Browse every note →
01
Complete series

External Perimeter Intelligence

5 parts77 min total
02
Complete series

macOS Security Boundaries

4 parts53 min total
03
Complete series

ATM Security Assessment

5 parts68 min total
04
Complete series

Browser-to-Native Trust Boundaries

3 parts51 min total
05
Complete series

When Access Checks Fail

3 parts25 min total
06
Complete series

Testing the Ransomware Playbook

5 parts34 min total
07
Complete series

Internal Network Triage

4 parts29 min total
Vulnerabilities

Published CVEs

Found during authorized testing, reported through coordinated disclosure.

View all →
Browser-local laboratories

Interactive Simulators

Zero-dependency security decision engines running directly in your browser. Test authorization boundaries, resolve Kerberos delegations, and verify policy logic in real time.

All tools →
Security engineering

Projects

Private products and public tooling built around problems I actually hit.

Public repositories →
Next.js + NestJS + Go01

XRAY ASM

A private, evidence-driven attack surface management workbench for discovering, relating, and prioritizing external exposure without confusing candidates with verified findings.

React + FastAPI + PostgreSQL02

GothamCity

A private adversary-emulation and detection-validation platform that turns ATT&CK techniques, Atomic Red Team tests, LOLBAS tradecraft, and controlled agents into measurable defensive coverage.

Go + TypeScript03

agentmordor

Evidence-backed authority mapping for AI agents — see which identity, tool, data, and external action are connected before deployment.

Markdown + Obsidian04

Methodology

A private operator knowledge system spanning 22 security domains, with one shared contract for authorization, evidence quality, false-positive review, proof of impact, and reporting.

Go05

ghostlink

Multi-channel Out-of-Band (OOB) covert C2 and data exfiltration framework over legitimate platforms, for authorized red team operations.

Swift06

evilcorp-ios

Intentionally vulnerable iOS benchmark application mapped to OWASP MASVS v2 & MASWE.

Go07

driftnet2

High-performance packet capture and credential extractor leveraging eBPF/XDP.

Python08

mcpbait

Red teaming framework for AI agents and Model Context Protocol (MCP) integrations — probes tool-use boundaries and prompt-injection paths.

Stay close to the work

New research, straight to your feed.

No newsletter, no tracking, no sign-up. Just the feed — or a direct line for disclosure and collaboration.

Subscribe via RSSGet in touch Quiet by design · updates only when the work is ready