🤖 RADHEY Selfbot — Telegram Userbot (Telethon)

A feature-rich Telegram userbot (selfbot) built with Telethon. It runs on your own Telegram account and lets you control it via dot-commands (.help, .info, .mute, .gc, etc.) sent from any chat. Includes a built-in web server for 24/7 hosting on platforms like Render.

⚠️ This is a userbot, not a Bot API bot. It automates a personal Telegram account using its API credentials. See Disclaimer before deploying.

---

✨ Features

Category	Commands
Help & Reliability	.help, .owner, .fix (auto-retry + error logging), .fixlog
User Info & OSINT	.info / .tinfo, .id, .chatinfo, .insta / .iginfo (Instagram profile lookup)
Moderation	.mute, .unmute, .ban, .unban, .block, .unblock, .kick, .admin, .demote
Messaging & Broadcast	.dm, .frwd (forward to all DMs), .gc (broadcast to admin groups), .broad (text-blast all users), .frwdall, .say (ghost-send)
Group Tools	.tag (mention all members), .autoaccept, .mm (create middleman group)
Utilities	.calc (SymPy-powered calculator), .tr / .translate, .count (countdown timer), .purge, .close, .del
Anti-ban	Randomized delays (5–10s) + forced 40s cooldown every 15 messages during broadcasts
Hosting	Built-in aiohttp health-check server (/ and /health) for uptime monitors / Render keep-alive

---

🛠️ Tech Stack

• Telethon — Telegram MTProto client
• aiohttp — lightweight keep-alive web server
• requests — Instagram GraphQL fallback + translation API calls
• sympy — safe math expression evaluation for .calc
• instaloader — primary Instagram profile scraper
• Flask — listed dependency (optional/legacy web layer)

---

📦 Installation

git clone https://github.com/<your-username>/<your-repo>.git
cd <your-repo>
pip install -r requirements.txt

Environment Variables

Never hardcode credentials in bot.py. Set these instead:

Variable	Description
API_ID	Telegram API ID from my.telegram.org
API_HASH	Telegram API hash from my.telegram.org
PHONE	Your account's phone number (with country code)
SESSION_STRING	(Optional) Base64-encoded Telethon session, for headless/server deploys without interactive login
PORT	(Optional) Port for the health-check server, defaults to 8080

Create a .env file or export them in your shell/host dashboard:

export API_ID="your_api_id"
export API_HASH="your_api_hash"
export PHONE="+1XXXXXXXXXX"

Run

python bot.py

On first run you'll be prompted for a login code (and 2FA password if enabled). A .session file is generated so future runs skip the login step.

Deploy (Render / VPS / Docker)

1. Generate a session string locally, base64-encode it, and set it as SESSION_STRING on your host — this skips interactive login on restart.
2. The app binds an HTTP health endpoint on $PORT, so it works out-of-the-box with Render's web service health checks.

---

💬 Usage

Send any command as a message from your own account (it works because outgoing=True events are captured):

.help
.info          (reply to a user)
.mute @someone
.gc            (reply to a message to broadcast it to groups you admin)
.calc sqrt(144) + 5
.tr hi Hello there

Full command list is always available in-app via .help.

---

⚠️ Disclaimer — Read Before Use

• Telegram's Terms of Service prohibit automating a personal user account (userbots/selfbots). Only bots created via @BotFather using the official Bot API are officially sanctioned. Using this script can get your account limited or banned — use at your own risk, ideally on a secondary/throwaway account.
• Mass-messaging features (.frwd, .gc, .broad, .frwdall) send unsolicited messages to your contacts/groups. Misuse of these can constitute spam and may violate Telegram's anti-spam policies as well as the platform policies of any group you're a member of. Use responsibly and only with recipients' consent.
• Remove all hardcoded secrets before publishing this repo. The original script contains a default API_ID, API_HASH, and PHONE inline in the source — treat any credentials that were ever committed as compromised, rotate them at my.telegram.org, and rely on environment variables going forward (see above). Also add *.session, selfbot_data.json, and errors.log to .gitignore, since they can contain live session tokens, muted/banned user IDs, and stack traces.
• Instagram scraping (.insta) uses unofficial/private endpoints and may break or get rate-limited if Instagram changes its API.

---

📁 Project Structure

.
├── bot.py              # Main userbot logic (commands, handlers, web server)
├── requirements.txt    # Python dependencies
├── selfbot_data.json   # Auto-generated: muted/banned user IDs (gitignore this)
└── errors.log          # Auto-generated: .fix error logs (gitignore this)

---

📝 License

Add a license of your choice (MIT recommended for open-source projects).

---

🏷️ Suggested GitHub Topics / Tags

telegram-bot  telethon  userbot  selfbot  telegram-userbot  python
telegram-automation  telegram-api  mtproto  automation-bot  osint-tool

---

🙋 Support

Questions or issues? Open a GitHub Issue in this repository.