A previous release had provenance metadata, but this release does not. View details.
th3LazySt4lker
A lazy approach to OSINT - because doing reconnaissance shouldn't require PhD levels of energy.
SOOOOOO I am really lacking sleep BUT!! We are on the first deployment :D This one actually works. No promises about the future though - ᴵ'ˡˡ ᵖʳᵒᵇᵃᵇˡʸ ᶠᵒʳᵍᵉᵗ ᵗʰᶦˢ ᵉˣᶦˢᵗˢ.
Installation
With Docker
git clone <repo> th3lazyst4lker
cd th3lazyst4lker
docker build -t th3lazyst4lker .
docker run --rm th3lazyst4lker --help
On Kali / Linux (Recommended)
if anybody can fix this I'll giv'em a lil' kiss
pip install st4lker
st4lker --help
OR
pip install st4lker --break-system-packages
st4lker --help
After install, st4lker works from anywhere (Probably).
Requirements
- Python 3.11+
- Linux (we don't do Windows here)
- pip
Usage
Standard Mode
Search by username:
st4lker -u admin
Search by email:
st4lker -e test@gmail.com
Search by name:
st4lker -n "John Smith"
High intensity (slower, more thorough):
st4lker -u admin -i 1
Check What Tools You Have
st4lker --check-tools
Get Help
st4lker --help
st4lker -h
Chaos Mode (The mess)
Run multiple tools with their specific parameters: (Haven't properly tested it and I coded this while really sleep deprived)
st4lker -chaos sherlock "admin" holehe "test@gmail.com"
Put each tool's arguments inside quotes. Chain as many as you want:
st4lker -chaos sherlock "--timeout 10 admin user1" holehe "test@gmail.com --only-used" socialscan "username1 username2" -r
The -r flag generates a text report at the end.
Tools Included
| Tool | Purpose |
|---|---|
| Sherlock | Username search across 500+ sites |
| Socialscan | Email/username availability checker |
| Holehe | Email breach detector |
| Maigret | Detailed username search (sherlock++ mode) |
| PhoneInfoqa | Phone number OSINT |
| Whois | Domain and IP lookup |
| Hunter | Email finder and verifier |
Intensity Levels
Use these with -i flag:
- 1 (High) - Thorough but slow, hits everything
- 2 (Medium) - Balanced (default)
- 3 (Low) - Fast, minimal requests
Use lower intensity if targets are rate-limiting you.
Examples
Quick username check
st4lker -u admin
Aggressive username search
st4lker -u admin -i 1
Email verification
st4lker -e test@gmail.com
Chaos mode with multiple tools and arguments
st4lker -chaos sherlock "--timeout 10 admin user1 user2" holehe "test@gmail.com" socialscan "username1 username2" -r
Custom tool arguments
st4lker -chaos sherlock "admin --csv" whois "example.com"
Project Structure
th3lazyst4lker/
├── st4lker/ (the actual package)
│ ├── __init__.py
│ ├── cli.py (main CLI interface)
│ ├── tools.py (tool management)
│ ├── colors.py (pretty output, just copy-pasted it from someone elses things)
│ └── reporter.py (report generation) (NOT TESTED ACROSS ALL FEATURES)
├── setup.py (pip setup)
├── requirements.txt (dependencies)
├── Dockerfile (for Docker lovers, also I used it because my VM got stuck)
├── .gitignore
└── README.md (this file, right here)
Contributing
Found a bug? Got a better idea? Want to add tools?
Go for it. PRs welcome. Don't expect super fast responses though, I will get to it when I remember I have an email.
Disclaimer
Use responsibly. This tool is for authorized reconnaissance and educational purposes only.
Don't do anything dumb (without getting me on it).
Made with blood, sweat, and tears excessive Monster energy.
(/^.^)/
Comments, bugs, and requests
- Discord: mrcyberandy
- Email: worriednerd@protonmail.com
Metadata
Release files for st4lker 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| st4lker-1.1.1.tar.gz | 10.4 kB | Without provenance | Details for st4lker-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| st4lker-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for st4lker-1.1.1-py3-none-any.whl |
Total release size: 20.1 kB
Release files / st4lker-1.1.1.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | st4lker-1.1.1.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
579fdc02811297ab36983aa09a9f96f219744c8e74c8b99e7b699a6f3862a5aa
|
|
BLAKE2b-256 checksum How to use checksums |
a41d480487b60bbfec1986987e995ffaecb973bc0a6c3169feb3930d299579ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.11
|
Release files / st4lker-1.1.1-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | st4lker-1.1.1-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
80fd087cc2c42d10b8253618109ca8c53ca3ead5da64f3445dec403672817ada
|
|
BLAKE2b-256 checksum How to use checksums |
ad4e0f63781bceb3cbe0de33fadad228b212f52543dd201af97ae271b799c89b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.11
|
Security for st4lker 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 1.0.2 2 files With provenance
- Added 1.1.1 2 files Without provenance
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.