Telepathy
2.3.4OSINT toolkit for investigating Telegram chats and accounts.
- Verified 24 Sept 2026
- pip 2.3.4
- MIT
- Dual-use
- Interactive
- Needs setup
Install and run
otlite install telepathyInstalls
telepathy==2.3.4into its own virtualenv. otlite lists what it will install and asks before it starts.otlite run telepathy -- tg:durovType your own value to rewrite the commands. It stays in this page: nothing is sent or saved.
telepathyreceivestelepathy -t durov
No otlite yet? Install it in one line
curl -fsSL https://get.otinstaller.com/otlite | shLinux and macOS, no Docker. It uses your Python and pipx when both are there, and otherwise brings its own Python. About otlite · otlite docs
Before you run it
- Dual-use. otlite prints this before installing it: You are solely responsible for how you use these tools and for complying with all applicable laws. Use them only on targets you are authorized to investigate.
- Asks questions while it runs. Run it on its own in a terminal;
otlite run --all,otlite autoand playbooks skip it. - Needs a login or API key. Set it up before the first lookup; batch runs skip it unless you pass
--include-credentialed. - Needs Python older than 3.13. Its googletrans and httpx dependencies use the cgi module, which Python 3.13 removed. otlite checks your Python before installing and says which version to use;
otlite doctorlists the tools your Python can't run.
Notes
- Asks for its Telegram credentials on the first run and stores them itself.
What it takes
Typed inputs after -- become Telepathy's own arguments. Anything else after -- passes through unchanged, so every option of the tool still works.
| Input | With otlite | telepathy receives |
|---|---|---|
Telegram nametg: | otlite run telepathy -- tg:durov | telepathy -t durov |
What a run leaves
Every run is saved under results/ where you run otlite (or --output, or OTLITE_RESULTS_DIR): what the tool printed, a sidecar with how it ran, and an envelope.
results/telepathy/durov/<time>_telepathy_durov_<run id>.txtresults/telepathy/durov/<time>_telepathy_durov_<run id>.meta.jsonresults/telepathy/durov/<time>_telepathy_durov_<run id>.envelope.json
{
"envelope": 1,
"tool": "telepathy@2.3.4",
"runtime": "otlite",
"input": { "target": "durov" },
"case": null,
"started_at": "…", "ended_at": "…", "duration_ms": …,
"exit_code": 0,
"status": "complete",
"entities": [{ "type": "url", "value": "…" }, …],
"warnings": [],
"output": { "path": "results/telepathy/durov/<time>_telepathy_durov_<run id>.txt", "sha256": "…", "bytes": … }
}otlite results --tool telepathyotlite extract telepathyotlite diff telepathy durovList the saved runs, pull out every indicator, or compare the two latest runs against the same target.
With other tools
Batch runs skip it: asks questions while it runs; run it on its own.