Estorides just surpassed LazyOwn in GitHub clones. The student has become the master (and I’m not even mad about it).
Estorides just surpassed LazyOwn in GitHub clones. The student has become the master (and I’m not even mad about it).
By grisun0 — Chief Architect of LazyOwn | Red Teamer | Professional builder of things that quietly eat public data for breakfast.
A few days ago I ran my usual masochistic command to check the breathing rate of my repositories:
Bash
USER=$(gh api user --jq '.login') && gh repo list --limit 150 --json name -q '.[].name' | xargs -I {} sh -c "echo -n '{}: ' && gh api repos/$USER/{}/traffic/clones --jq '.count' 2>/dev/null || echo 0" | sort -t: -k2 -nrThe output hit different this time:
- estorides: 651
- LazyOwn: 510
Yes, the side quest I started because I was tired of duct-taping random OSINT scripts together has now officially out-cloned the mothership. The universe clearly enjoys irony more than I do.
The problem that started it all
As a red teamer, I live in the reconnaissance phase more than anywhere else. I needed something fast, clean, truly passive, and actually useful. No noisy active scanning that lights up every SIEM from here to Beijing. Just high-quality open source intelligence, well collected, well correlated, and ready to feed the rest of the engagement.
I already respected how LazyAddons worked inside LazyOwn — modular, extensible, and not pretending to be something it’s not. So the logical (some would say lazy) next step was to take that philosophy and scale it aggressively.
That’s how Estorides was born.
From addon spirit to full OSINT engine
I fused the LazyAddons model with everything I wished existed for passive recon:
- 99+ passive OSINT sources (and growing) across DNS, IP space, web artifacts, social footprints, threat intelligence, breaches, geo data, blockchain, leaks, certificates, and more.
- Proper asynchronous fanout with retries, circuit breakers, and intelligent caching (SQLite by default).
- Structured parsers that actually turn raw data into something you can use instead of dumping JSON hell at you.
- A knowledge graph built with NetworkX, complete with GraphML export and visualization.
- Multi-backend LLM analyst support (Ollama, OpenAI, Anthropic, Grok, whatever you trust least this week).
- Web UI that includes interactive maps, graph views, timelines, and clean exports (including STIX and MISP formats).
- Everything designed to stay passive. No heroic port scanning. Just public data, orchestrated like it should be.
The name? Estorides. Because we’re out here catching every open intelligence source we can find, Pokémon-style. Each new source is another entry in the Pokedex. The plumbing is clean enough that adding the next one is mostly a matter of dropping a well-structured YAML and a parser. Exactly like the lazyaddons approach, but dialed up.
Why it seems to be resonating
People are actually using it. A lot. Which is the best kind of validation.
Get Lazyown Redteam’s stories in your inbox
Join Medium for free to get updates from this writer.
It solves a real pain point I had: I wanted reconnaissance that felt more like research and less like throwing darts at Shodan while hoping nothing breaks. And apparently I’m not the only one tired of noisy, half-baked tools.
So I’ll keep feeding it:
- More sources
- Better relationship inference and correlation
- Improved visualizations
- More automation options
- Tighter integration with the rest of the LazyOwn ecosystem
Because if it fixes my workflow, there’s a decent chance it can fix yours too.
What you actually get (no marketing fluff)
- Clean CLI that doesn’t fight you.
- install.sh or pip for the impatient.
- Modular architecture so you can extend it without rewriting the core.
- Cache layers that actually save you time and API rate limits.
- Outputs you can feed directly into other tools or your own analysis pipeline.
Repo: https://github.com/grisuno/estorides
Try it. The installation is boringly straightforward, which is exactly how I like my tooling foundations.
Next steps for Estorides: keep expanding the source list, sharpen the inference engine, and continue turning it into the passive recon tool I wish I had years ago.
If you’ve already played with it, tell me the unfiltered truth in the comments — what worked, what hurt, what’s missing. If you have a favorite OSINT source that should be in the Pokedex, drop it in the issues. This thing grows best when it’s solving actual problems instead of chasing hype.
Stay sharp out there. grisun0 — still collecting public data that probably shouldn’t be this easy to find.
