otinstaller · Username
Install Aliens Eye on Linux in one command
Aliens Eye searches a username across several hundred social sites and reports the matches. Its site list overlaps Sherlock's, so it mostly serves as a cross-check.
Aliens Eye in three lines
pipx install otinstaller
ot install aliens-eye
ot run aliens-eye -- u:jane_doeRuns arxhr007/Aliens_eye (MIT, ★ 4.1k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.
What Aliens Eye is for
- A cross-check on Sherlock and Nexfil output.
- Handles on smaller regional sites.
Typed inputs for Aliens Eye
otinstaller translates these prefixes into Aliens Eye's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- u:
- username ·
ot run aliens-eye -- u:jane_doe
Run every installed tool that takes the same input at once: ot run --all u:jane_doe
Where the results go
Every run lands under ./results/aliens-eye/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff aliens-eye <target>, and pull indicators out with ot extract.
Before you run it
- Treat results as leads; the detection rules are community maintained.
Update, remove, inspect
ot info aliens-eye # inputs, flags, keys
ot example aliens-eye # sample output
ot update aliens-eye # move to the next tested version
ot remove aliens-eye # delete its virtualenvFull reference for this tool: docs for aliens-eye.
Pairs with
FAQ
Aliens Eye with otinstaller, answered
How do I install Aliens Eye on Kali or Ubuntu?
Install otinstaller once with pipx install otinstaller, run ot init, then ot install aliens-eye. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.
Which inputs does Aliens Eye take through otinstaller?
u: (username). otinstaller maps each prefix to Aliens Eye's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.
Where does otinstaller save Aliens Eye results?
Under ./results/aliens-eye/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot diff aliens-eye <target> to compare the last two.
Does Aliens Eye need an API key or a login?
No key is required for the basic run. Optional keys, where the project supports them, go in ~/.otinstaller/.env and are passed only to tools that declare them.
Can I run Aliens Eye together with other tools?
Yes. ot run --all u:jane_doe runs every installed tool that accepts username input, in parallel, including Aliens Eye. Save the combination as a playbook to repeat it.