Dearen Kansil
Security Research · Open-Source Tooling
Integrity Verification · Detection · Forensics
I research how systems fail, then I build the tools that catch it. Most of my work starts as offensive research - enumerating, exploiting, understanding what breaks - and ends as a defensive tool anyone can run. Everything I ship is open source, documented, and free.
research → tooling
I'm an Informatics Engineering student working on offensive security. Most of what I know, I learned by breaking things in labs, CTFs, and on my own infrastructure - enumerating networks, testing web applications, and working through privilege escalation until I understood not just that something failed, but why.
That research turned into tooling. Once I kept re-solving the same problems, I started writing the tools instead - small, focused utilities that anyone can run against their own systems. Everything is open source, because a detection tool nobody can inspect is just another thing you have to trust blindly.
I now work on both sides of that loop: building defensive tools and running assessment support engagements. If you have a specific workflow that needs a tool, or you want to learn offensive security properly rather than from a checklist, get in touch.
free · open source · self-hosted
T-01
A Python CLI tool for generating and verifying file and directory integrity using cryptographic hashes, with baseline manifests and recursive verification.
Use case Establish a known-good baseline, then prove whether anything on a host changed since. Useful for forensics, compliance checks, and incident response triage.
T-02
In active research. Each tool here started as a problem I hit repeatedly during assessment work, so this one will too — details land when it's usable.
T-03
In active research. Each tool here started as a problem I hit repeatedly during assessment work, so this one will too — details land when it's usable.
T-04
In active research. Each tool here started as a problem I hit repeatedly during assessment work, so this one will too — details land when it's usable.
T-05
In active research. Each tool here started as a problem I hit repeatedly during assessment work, so this one will too — details land when it's usable.
No project matches that tag.
custom work alongside open source
S-01
A small, focused utility built around your actual workflow - not a repackaged framework. Scoped tight, documented, and handed over as a repo you own.
S-02
Scoped web application and network testing with written findings. Useful when you need a second set of eyes on an engagement or want findings you can hand to a team.
S-03
Hands-on sessions built from real labs and CTFs, focused on understanding the reasoning behind each step rather than memorising a checklist.
click a card to view it full
Accepting custom tool requests
Tell me what you're trying to do and what's getting in the way. If I can build it, I'll tell you what it takes; if I can't, I'll say so rather than waste your time.
