kevin/thecrewx

Security & systems developer

I build defensive security tooling — and the automation around it.

Frameworks, honeypots, and device toolkits for security research and day-to-day operations. Mostly Python and C#, with Rust and Go where it counts.

  • Reverse engineer
  • All-'rounder development
  • Research spy
See the work GitHub
thecrewx — zsh
$ whoami kevin — thecrewx Security & systems developer · France · UTC+1 $ focus defensive security · systems · automation $ status open to collaboration

Try help · projects · theme

Based in
France · UTC+1
Primary
Python · C# · Rust
Focus
Defensive tooling
Repositories
5 public
Selected work

Five things worth looking at.

Tools I maintain and use, not demos. Each one has a page explaining why it exists and the decisions behind it.

Featured · Security framework

aegiscore

A modular security framework that gives detection, response, and reporting a single spine instead of a folder of disconnected scripts.

  • Python
  • Modular core
  • Active
Read the write-up

shadowgate

02

A honeypot and network-monitoring layer that records what reaches it and turns background scan traffic into something readable.

Language
Python
Domain
Network security
Read more

phonesurgeon

03

An Android device toolkit wrapping roughly 200 ADB operations behind one interface, with the destructive ones clearly marked.

Language
Python
Domain
Device toolkit
Read more

phish-lab

04

A closed research environment for studying credential-phishing patterns and building material that helps people recognise them.

Language
HTML
Domain
Security research
Read more

toolskit

05

Sixteen focused automation modules for Windows housekeeping, collected behind one interface instead of scattered across a scripts folder.

Language
C#
Domain
Automation
Read more
About

Minimal by default.

I'm thecrewx, a Crew Developer.

I build clean, efficient tools — browser extensions, CLI utilities, and full applications — and I enjoy turning a rough idea into something people actually use.

  • Minimal by default: fast, functional, no bloat
  • Comfortable across the stack, happiest close to the tooling layer
  • Shipping small products that solve real problems
Objective

Open to interesting collaborations, freelance work, and opportunities where I can build things that matter.

Based
France · UTC+1
Primary
Python · C# · Rust
Also
Go · C/C++ · TypeScript
Focus
Defensive tooling
Repositories
5 public
Status
Open to work

Path so far

  1. Now

    Frameworks over one-off tools

    Consolidating years of scattered scripts into maintained projects with real interfaces, guardrails, and documentation — aegiscore and shadowgate are where most of that effort goes.

  2. Recently

    Defensive security focus

    Moved deliberately toward the defensive side: honeypots, detection tooling, and awareness material. Understanding offensive technique matters, but the work I want to ship is the part that helps people notice and respond.

  3. Before that

    Automation as a habit

    Started collapsing repetitive operational work into tools — device management, Windows housekeeping, anything done more than twice. This is where phonesurgeon and toolskit came from.

  4. The start

    Breadth first

    Worked across the whole range on purpose: browser-side interfaces, systems-level code in C and C++, and scripting in between. That breadth is why moving between a web view and a systems problem is not a context switch.

What I do

Tools, not demos.

Three areas where I do my best work — and the kind of problems worth bringing to me.

Security tooling

Detection and response tooling built to be maintained rather than demoed — modular, testable, and honest about what it did not check.

  • Modular frameworks
  • Honeypots & telemetry
  • Reporting pipelines

Automation

Repetitive operational work turned into tools with dry runs, clear reporting, and confirmation on anything that cannot be undone.

  • Device & fleet tooling
  • System housekeeping
  • CLI interfaces

Systems work

Comfortable from the browser down to systems level, which means the right layer gets chosen for the problem rather than for familiarity.

  • Python, C#, Rust, Go
  • C / C++ where needed
  • Interfaces & tooling
Writing

Notes from the build.

What broke, what I changed, and what I would do differently — written while it was still fresh.

Reading honeypot noise

A public honeypot collects an enormous amount of traffic that means almost nothing. The useful work is not capture — it is compression.

7 min read

ADB at scale, without wiping the wrong phone

Wrapping around 200 ADB operations taught me that the interesting engineering is not the commands — it is the guardrails and the parsing.

6 min read

A framework beats twelve scripts

Twelve scripts that each work fine will still fail you together. What they lack is not features — it is shared conventions.

8 min read

All writing

Stack

A toolbox built for range.

Breadth on purpose. Being comfortable from the interface down to systems level means picking the right layer, not the familiar one.

Interface

  • HTML
  • CSS
  • JavaScript
  • TypeScript
  • Tailwind

Core & systems

  • Python
  • C#
  • C++
  • C
  • Rust
  • Go
  • Java
  • PHP
  • Lua

Tooling

  • Git
  • Docker
  • Bash
5+ Public projects
12 Languages & tools
200+ ADB commands
16 Toolkit modules
Contact

Got something worth building?

Open to interesting collaborations, freelance work, and opportunities where I can build things that matter. GitHub is the fastest way to reach me.

github.com/thecrewx Instagram