Skip to content

🛡️ TeamTalk5 IP Guard Bot — v2.0

kotIpGuardBot

 

«IP Intelligence, Anonymity Control & Geo-Watchdog»
🚀 Developed by @kotafe24 | 🧠 Powered by Firebase + IPLocate API


🔧 What This Bot Does

This bot is a TeamTalk5 server assistant designed for IP monitoringanonymity detectiongeo-location lookup, and flood protection.

It automatically:

  • Detects anonymous logins (users with no username)

  • Sends geo-location details (country, city, ISP, domain, etc.) upon user entry

  • Auto-mutes anonymous users in public rooms

  • Provides admin commands to control security features

  • Supports whitelist, blacklist, and custom mute rooms

  • Logs & bans users with IP flood attempts

  • DDoS protection logic with live toggling

  • Displays connected user information via ? command

  • Has VIP bypass for trusted users


🌍 Real-Time Geo Intelligence

When a new user joins a monitored channel, the bot performs:

  • 🌐 IP Geo-location lookup via iplocate.io

  • 📡 Detection of VPNs / proxies

  • 🗺️ Fetches: country, city, ISP, domain, ASN name

  • 🔊 Sends this info to all subscribed channels (Firebase-powered)


👤 Anonymous Detection

If a user logs in without a username, the bot:

  • Tracks their login attempts

  • If LoginFlood is enabled:

    • After 5 logins in 3 seconds (configurable), the bot bans by IP

  • If EnableSpam is enabled:

    • Auto-mutes anonymous or black listed users in selected channels or lobby


🔒 VIP Protection

Users in the Firebase list IP_BOT_BypassList are considered VIPs.
They are:

  • 🎉 Welcomed with a special message: «🛡️ Protected VIP profile 🔐»

  •  By-passed from IP public tracker

📦 Firebase Settings

The bot fetches all live configuration from Firebase Realtime Database:

  • Channels to announce in

  • Server IP & ports

  • Blacklists, whitelists, mute rooms

  • Public data display settings (Geo, Client version, etc.)

  • Anti-flood values

  • Channel join name and password

You can update configuration remotely via Firebase anytime 🔁


🔑 Admin Features

Admins can control the bot by sending commands
A user is considered admin if:

  • They are listed in WhiteList (Firebase)

  • OR they have admin flag (uUserType == 2)

    🔑 Admin Features & Commands

    Command Access Description
    ? Anyone See own IP, geo, version info
    ?? Anyone Show full command list
    + Admin/White list user  🔇 Anonymous voice OFF
    - Admin/White list user 🔊 Anonymous voice ON
    ++ Admin/White list user ✅ Flood detection ON
    -- Admin/White list user  Flood detection OFF
    +++ Admin ✅ Activate DDoS protection
    --- Admin  Deactivate DDoS protection
    xxx Admin 🔁 Reboot the bot

    📶 Live Status in TeamTalk

    The bot automatically updates its status message to reflect all protection states:

    Anonymous Flood DDoS Bot Status Message
    🔊 Anonymous 🔊 Flood ❌ DDoS❌
    🔊 Anonymous 🔊 Flood ✅ DDoS❌
    🔇 Anonymous 🔇 Flood ❌ DDoS❌
    🔇 Anonymous 🔇 Flood ✅ DDoS❌
    🔊 Anonymous 🔊 Flood ❌ DDoS✅
    🔊 Anonymous 🔊 Flood ✅ DDoS✅
    🔇 Anonymous 🔇 Flood ❌ DDoS✅
    🔇 Anonymous 🔇 Flood ✅ DDoS✅

     

    💬 Example Auto-Messages

    Anonymous  join:

    UserID: 3367

    Country:Portugal

    City:Porto

    Provider:MEO — SERVICOS DE COMUNICACOES E MULTIMEDIA S.A.

    Net:MEO-RESIDENCIAL

    Domain:novobanco.pt

    Version:332288

    Client:TeamTalk5 (macOS Sequoia (15.4))

    VIP join:

    safeacid — 🛡️ Protected VIP profile 🔐

 

Example of JSON file to be uploaded to Realtime Database

{
«IP_BOT_AntiSpam»: {
«Duration»: 3,
«TimesLogin»: 5
},
«IP_BOT_BlackList»: [
«»,
«open»,
«guest»
],
«IP_BOT_BypassList»: [
«kotjara»,
«contabo»,
«safeacid»
],
«IP_BOT_Channels»: [
«/»,
«IT»,
«! Xвосты без дела ✨»,
«!Jazz Cafe🎷»,
«!Nekto + 1 💬»,
«!Два Хвоста🐾🐾»,
«!Душный разговор 🧘‍♀️»,
«мур-мяу😍»
],
«IP_BOT_GEO_API»: «aeb8cf4e9a169fe876abe97e9df371b9»,
«IP_BOT_MuteRooms»: [
«»,
«/»,
«! Хорошее Настроение»
],
«IP_BOT_Server»: {
«ChannelName»: «/IT»,
«ChannelPassword»: «»,
«host»: «tt5.live»,
«password»: «general»,
«tcpPort»: 10333,
«udpPort»: 10333,
«username»: «xarcok»
},
«IP_BOT_WhiteList»: [
«kotjara»
],
«IP_BOT_public_show_list»: {
«s_city»: false,
«s_client»: true,
«s_country»: false,
«s_domain»: true,
«s_network»: true,
«s_nickname»: true,
«s_provider»: true,
«s_username»: true,
«s_version»: true
}
}

 

Legend:

🔐 IP_BOT_Server

Settings required to connect the bot to a TeamTalk server:

  • host: The TeamTalk server address (e.g., tt5.live)

  • tcpPort / udpPort: Ports used for TCP and UDP connections

  • username: Bot’s login username

  • password: Bot’s login password

  • ChannelName: The main channel bot will join (e.g., /IT)

  • ChannelPassword: Password for that channel (optional)


📣 IP_BOT_Channels

A list of TeamTalk channels where the bot will broadcast messages (e.g., join/leave notices, GeoIP info).


🛑 IP_BOT_BlackList

List of usernames that are banned or treated as suspicious. Their voice may be disabled on entry to specific rooms.


IP_BOT_WhiteList

List of trusted usernames allowed to control the bot via admin commands (e.g., enable/disable spam protection).


🥷 IP_BOT_BypassList

Usernames that are considered VIPs — these users will not be muted or analyzed, and get a welcome message when joining.


🔇 IP_BOT_MuteRooms

Channels where the bot will automatically mute anonymous or blacklisted users upon entry.


🌍 IP_BOT_GEO_API

Your API key used to fetch IP geolocation data (e.g., country, city, ISP, VPN status, etc.).


🛡️ IP_BOT_AntiSpam

Flood control parameters:

  • Duration: Timeframe in seconds to monitor login attempts (e.g., 3 seconds)

  • TimesLogin: Number of allowed logins in that timeframe before temporary IP ban


🕵️ IP_BOT_public_show_list

Flags for what information should be included in public messages (shown when users join a channel):

  • s_username: Show TeamTalk username

  • s_nickname: Show nickname

  • s_country / s_city: Show geolocation info

  • s_provider: Show ISP name

  • s_network: Show ASN/network name

  • s_domain: Show domain (if available)

  • s_version: Show client version

  • s_client: Show client name