Specialized offensive security developer focused on Red Team automation and vulnerability research using Go and Java. Demonstrates deep understanding of low-level network protocols and exploit chains, creating operational tools that prioritize stealth and efficacy over software engineering polish.
Score Context: Score reflects deep expertise in offensive security and systems programming, but is tempered by a lack of software engineering rigor. The developer excels at operational efficacy and research but prioritizes functionality over maintainability and testing.
Red Team Automation tool powered by go and terraform
Most common theorical Web RCE's with some "testing code" and PoC's to practise with (not real CVE's)
Golang Source Code Modifications to add features
Repositories consistently lack automated unit tests, with explicit 'TO-DO' comments highlighting this gap.
Projects feature comprehensive READMEs and high-quality inline comments that explain complex attack logic.
Logical separation of concerns is present (e.g., build tags for OS-specific code), but relies heavily on brittle global state.
Frequent code duplication and usage of hardcoded paths/values significantly hamper long-term maintenance.
Demonstrates advanced knowledge in architecting C2 channels (SiestaTime) and weaponizing RCE vulnerabilities.
Capable of complex systems programming and modifying standard libraries (crypto/tls), though struggles with state management.
Deep low-level understanding shown by implementing custom SSH handling and TLS fingerprint manipulation (JA3 spoofing).
Functional understanding of Java web stacks and serialization exploits, but projects lack standard build tooling (Maven/Gradle).
Extensive cataloging of CVEs and creation of educational Proof-of-Concept exploits across multiple languages.
Get docs, diagrams, scorecards, and reviews for any repository. Understand code faster.