SARKAR MD is a third party WhatsApp Multi Device bot project by Sarkar Bandaheali, built on the Baileys library and presented by its README as version 3.0.0, the Neon Edition. The first fact a reader needs is where the code can still be read: the original GitHub repository returns a 404 error today, so this guide is checked against the public fork under the miank account, whose GitHub metadata names the original repository as its parent and which carries the full README, the configuration files and a LICENSE file. Both pair code services the README links return a 404 error today and the project website listed in the repository metadata does not load, so this guide links no session service for SARKAR MD as a working service.
By AHMED X · November 7, 2026 · Last verified November 7, 2026
About
What the project is, who developed it, where its code can still be read today, and the version presentation its README gives it.
SARKAR MD is a third party WhatsApp Multi Device bot project associated with Sarkar Bandaheali. The repository description carried by the surviving fork reads, in the project own words, Tech ka Jugaadu, Future ka Baap, with AI strength and a desi style, and the README header presents SARKAR-MD as an ultimate WhatsApp bot with Multi Device support, powered by Baileys and described as fast, secure and reliable. The package file and the app.json file both use the Bandaheali name: the package file gives its author as Bandaheali, and app.json describes the app as a WhatsApp bot made by Bandaheali.
The original repository, Sarkar-Bandaheali/Sarkar-MD, cannot be read today. Its GitHub page returns a 404 error and the GitHub API reports it as not found. A second address the README deploy buttons point at, Bandaheali/Sarkar-MD, also returns a 404 error today. The record that survives in full is the public fork at miank/Sarkar-MD: the GitHub API confirms that this repository is a fork and names Sarkar-Bandaheali/Sarkar-MD as its parent, and it carries the complete README, the configuration files, the deployment files and a LICENSE file. Another fork exists under the Sujaysujay52 account, but its README is only a short stub, so every fact in this guide is checked against the miank fork. Nothing from unrelated bots that share the Sarkar name is merged into this guide.
On version, the README speaks in two places. Near the top it states the current bot version as 3.0.0, and a status block near the end reads Project Status Active, Version 3.0.0 Neon Edition. The package file in the same repository carries a different version value, 10.8.1, with main.js as its main file. This guide reports both values exactly as they stand: 3.0.0 Neon Edition is the version presentation the project gives its readers, and 10.8.1 is the version string its package file ships.
The repository tree of the fork holds the full application: main.js as the entry point named by the package file, a SarKar.js file beside it, config.js and config.cjs as configuration files, an .env file, a session folder, a lib folder of helper modules covering areas such as welcome messages, warnings, sudo users and anti bot behaviour, a main.html file, and the deployment and project files package.json, Dockerfile, Procfile, app.json and LICENSE. The README also links a support WhatsApp channel for the project.
Features
The README publishes one short feature list and nothing more: no command list, no command categories and no prefix appear anywhere in it. The cards below cover only that documented list, with the AI model count presented as the claim the README itself makes.
The README feature list names antidelete as a headline feature. In the project own framing, this is the protection that concerns messages deleted after they were received. The README gives no configuration detail for it.
The same list names antiviewonce, the protection that concerns view once media. The README states the feature name and explains nothing further about how it behaves or how it is set up.
Antilink completes the protection trio in the README list. It is the feature aimed at links posted in chats the bot watches, and again the README documents the name only, with no settings or permissions explained.
The README lists high speed downloaders for four services: YouTube, TikTok, Facebook and Instagram, written in its list as YT, Tiktok, FB and IG Downloaders. High speed is the project own wording. The README names no supported formats and no command names for these downloaders.
The README claims support for more than ten AI models, written in its list as 10+ AI models. That count is a claim the project makes about itself: the README names none of the models and gives no availability detail, and this guide presents the number only as that claim, never as a counted fact.
Beside the model count, the README lists image analysis AI as its own feature. It does not name the service behind the analysis or explain what a user sends or receives, so this guide records the feature exactly at the level the README documents it.
The README describes the interface as a futuristic and cool icy UI, and presents the bot as fast, powerful and of low latency. Those are the project own presentation claims about its look and speed, recorded here as claims rather than as measured results.
Session ID
The README Get Session ID section carries two buttons, labelled LINK 01 and LINK 02 in its text and PAIR CODE 1 and PAIR CODE 2 on the buttons themselves. The real destinations behind those buttons were read from the raw README source for this guide, and both services were opened again today. Both return a 404 error, so this section records the documented route and states its present day condition plainly.
Open the miank/Sarkar-MD repository, which carries the full README, and find the deployment steps. Step 2 of those steps is headed Get Session ID, and it holds the only two authentication links the project publishes.
The first button points to sarkar-md-session-generator.koyeb.app, a session generator hosted on Koyeb. A service of this kind asks for a WhatsApp number with its country code and returns a pairing code to type into WhatsApp.
That address was opened again for this guide and returns a 404 error page stating that there is no active service. The first documented pairing route for SARKAR MD does not work today.
The second button points to sarkarmd-session-generator.onrender.com, a session generator hosted on Render, presented as the alternative pairing route when the first one fails.
That address was also opened again for this guide and returns a plain 404 Not Found response. The second documented pairing route does not work today either, so no working official session service for SARKAR MD could be confirmed. This guide links neither address as a working service.
The general flow behind a pair code service is: enter your WhatsApp number with its country code, request the code, open WhatsApp, go to Linked Devices, choose the option to link with a phone number instead, and enter the code before it expires. The README adds its own note that connection issues may require a VPN to be active.
The project consumes a Session ID value: app.json lists SESSION_ID as a required setting with a description telling the user to paste the Session ID they obtained, and config.js reads SESSION_ID from the environment. The repository also carries a session folder. Keep the exact value private, because anyone holding working session credentials may be able to access the WhatsApp session they came from.
With both documented services down and the original repository gone, any unrelated website using the SARKAR MD name to offer session generation is not backed by project documentation this guide could check. Never type your number into such a page and never pay for a session for this bot.
Deployment
The README gives a fork step and a session step and then a Deployment Options section made of badge buttons. This guide presents deployment only at the level the surviving files prove: the files that are present in the repository tree, what each of them shows, and the present day state of the routes the README buttons point at.
The original repository the README fork button points at returns a 404 error today. Work from the readable miank fork, whose metadata names the original as its parent, and expect the documentation of a project in this state to contain dead routes, as its session section already shows.
The README first deployment step is to star and fork the repository. In the fork tree, the files a deployer meets are package.json with the start scripts, config.js and config.cjs for settings, an .env file, the session folder, and the deployment files named in the steps below.
app.json names the settings the app asks for at deploy time. SESSION_ID, MODE, OWNER_NUMBER and OWNER_NAME are listed as required, and a set of optional automatic behaviour toggles follows. Replace every shipped example value with your own, as the configuration section below records.
The repository tree contains a Dockerfile, which is the file a container based environment uses to package the application and its dependencies. Its presence is file evidence that a container route was prepared by the project. The README gives no Docker commands, so this guide publishes none.
The tree also contains a Procfile and app.json. app.json describes a single worker formation and lists buildpacks for Node.js, ffmpeg and webp, which is the shape of a Heroku style deployment prepared in files. That is the extent of what the files prove, and no working template route is claimed.
Checked against the actual tree of the readable fork, three files that summaries of this project sometimes list are not there: the tree contains no heroku.yml file, no render.yaml file and no start.sh file. Any deployment description built on those files does not match the repository as it survives today.
The Deployment Options section of the README is a table of badge buttons naming hosting providers. The template links behind those buttons point at the Bandaheali/Sarkar-MD address, which returns a 404 error today, so none of those documented routes can be followed as written. This guide therefore presents no provider procedure for SARKAR MD.
The package file start script runs the bot under PM2: it starts main.js with the process name Sarkar-MD and attaches to it, and stop and restart scripts for the same PM2 process sit beside it. On a machine of your own, those scripts are the run method the project files themselves define, after dependencies are installed and the session setting is in place.
Configuration
The settings below are the ones app.json actually lists, checked against the file in the readable fork, together with the configuration files the tree contains. Follow the exact names the files use and replace every shipped example value with your own.
The first setting in app.json and the only credential the app requires. Its description tells the user to paste the Session ID they have obtained. config.js likewise reads SESSION_ID from the environment, so every run route depends on this one value being present and private.
A required setting in app.json. Its description explains the value chooses between public mode and private mode for the bot, with public given as the shipped value in the file.
Both are required in app.json: the owner phone number, which the file description says should be given with its country code, and the owner name, which ships with the Bandaheali name as its value. Every deployer replaces the number with their own.
app.json lists optional toggles named AUTO_STATUS_SEEN, AUTO_READ, AUTO_TYPING, AUTO_RECORDING and ALWAYS_ONLINE, covering automatic status viewing, message reading, typing presence, recording presence and an always online presence. Each takes a yes style or no style value in the wording of the file.
Two more optional settings in app.json are AUTO_BLOCK, described as an automatic block rule tied to a country code prefix the file names, and REJECT_CALL, which controls automatic call rejection. Both ship in the off position in the file values.
The tree carries config.js, a config.cjs file beside it and an .env file, and config.js reads its session and owner settings from environment variables. Because more than one fork of this project circulates and their configuration files are not identical, always follow the files inside the exact copy you downloaded rather than settings lists copied from elsewhere.
Official Links
The resources checked for this guide: the fork that carries the full surviving record, the project channel its README links, the library the bot is built on, and the documented addresses that no longer load, listed for the record with their check results stated honestly.
The miank/Sarkar-MD repository, a public fork whose GitHub metadata names Sarkar-Bandaheali/Sarkar-MD as its parent. It carries the full README, config.js, package.json, app.json and the LICENSE file this guide verified against.
https://github.com/miank/Sarkar-MD
The Sarkar-Bandaheali/Sarkar-MD address the project badges and fork button point at. It returns a 404 error today on the web and through the GitHub API, and is listed for the record, not as a working source.
https://github.com/Sarkar-Bandaheali/Sarkar-MD
The WhatsApp channel the README links under its Support Channel heading, presented there as the place to follow the project.
https://whatsapp.com/channel/0029VajGHyh2phHOH5zJl73P
The current home of the Baileys library under the WhiskeySockets name. The package file of SARKAR MD lists the WhiskeySockets Baileys package among its dependencies.
https://github.com/WhiskeySockets/Baileys
The bandaheali.site address listed as the homepage in the repository metadata. It did not load when checked for this guide, closing the connection without a response, and is listed for the record, not as a working site.
https://bandaheali.site
The Koyeb hosted pair code service behind the first README session button. It returns a 404 error page stating there is no active service, checked for this guide, and is listed for the record, not as a working service.
https://sarkar-md-session-generator.koyeb.app/
The Render hosted pair code service behind the second README session button. It returns a 404 Not Found response, checked for this guide, and is listed for the record, not as a working service.
https://sarkarmd-session-generator.onrender.com/
Safety
The precautions that apply to SARKAR MD, including the warning its own README prints, the risks created by its dead session services and gone original repository, and the disagreement inside its license records.
SARKAR MD is an unofficial third party bot, and its README prints the warning itself: this bot is not affiliated with WhatsApp Inc, use is at your own risk, and misuse may result in account bans. Take that warning at face value. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect, and no feature in any bot can promise protection from that. Use a separate number for testing rather than your main personal or business number, and avoid spam and abusive automation of any kind.
Understand the present day state before connecting anything. The original repository is gone, both pairing services the README publishes return 404 errors, the project website listed in the repository metadata does not load, and the routes in the README deploy buttons point at a repository address that is also gone. A vacuum of this kind is exactly what fake session websites exploit. Only trust authentication links you can trace back to project documentation, and treat every other SARKAR MD session page as unverified.
Check the shipped files before you run anything. The configuration files in circulating copies carry shipped default values, including an owner number value written into the code, and those values belong to the project side and must be replaced with your own before any run. Never use credentials or numbers you find inside a public repository, and never share your own Session ID in chats, screenshots or public forks. On licensing, the records inside the readable fork disagree with each other in three places: the LICENSE file in that fork carries the full MIT License text with a 2025 copyright line for Sarkar Tech, and the GitHub API detects MIT for that fork, while the status block at the end of the same README names the license as Apache and the license field of package.json reads ISC. Because the original repository cannot be opened, its own LICENSE file cannot be checked at all. This guide reports all three signals exactly as they stand and names no single license for SARKAR MD, so readers should not assume any one of them governs the code.
Alternatives
Want more free MD bots like this? These bots on AHMED X cover the same ground: free deploy, pair-code setup, group and chat automation.
ASTRA X
WhatsApp MD Bot
Advanced AI-first MD bot with dual AI engines, media downloaders and deep group management.
Geston-MD
WhatsApp MD Bot
Lightning-fast Baileys multi-device bot with AI chat, group protection and replies in many languages.
CELESTIA
WhatsApp MD Bot
A polished multi-device WhatsApp bot with a large command library, AI chat and safe group tools.
TOXIC-MD
WhatsApp MD Bot
Lightning-fast WhatsApp bot built on Baileys, made for speed and everyday automation.
SUKUNA-MD
WhatsApp MD Bot
A modular WhatsApp MD bot with group administration, media tools, protection engines and AI voice replies.
Levanter
WhatsApp MD Bot
Multi-device WhatsApp bot packed with group protection, AI chat and a plugin system.
FAQ
Short answers to the questions readers ask most about SARKAR MD.
SARKAR MD is a third party WhatsApp Multi Device bot project associated with Sarkar Bandaheali and built on the Baileys library. Its README documents message protection features, media downloaders for YouTube, TikTok, Facebook and Instagram, an AI model claim and image analysis AI, and presents the project as version 3.0.0, the Neon Edition.
The project is associated with Sarkar Bandaheali. The fork metadata names the Sarkar-Bandaheali repository as the original, the package file gives its author as Bandaheali, app.json describes the bot as made by Bandaheali, and the LICENSE file in the surviving fork carries a copyright line for Sarkar Tech.
No. The Sarkar-Bandaheali/Sarkar-MD address returns a 404 error today, on the web and through the GitHub API, and the Bandaheali/Sarkar-MD address its deploy buttons point at is also gone. The full record survives in the public fork at miank/Sarkar-MD, whose metadata names the original as its parent, and this guide is checked against that fork.
The README presents the project as version 3.0.0 and its status block calls it the 3.0.0 Neon Edition, with the project status given as active. The package file in the same repository ships a different version value, 10.8.1. This guide reports both exactly as they stand rather than choosing between them.
Only what its README lists: antidelete, antiviewonce and antilink; downloaders for YouTube, TikTok, Facebook and Instagram; a claim of more than ten AI models, presented in this guide as the project own claim because the README names none of them; image analysis AI; and a futuristic user interface with fast and low latency presentation claims.
The README publishes no command list at all, and no command names, categories or prefix appear in it, so this guide publishes none. Any command list for SARKAR MD found elsewhere does not come from the project README this guide could check, and the configuration files of the circulating copies are not identical, so settings taken from another copy may not match yours.
The documented route is the Get Session ID section of the README, which holds two pair code buttons. The first points to a session generator on Koyeb and the second to one on Render. Both were opened again for this guide and both return a 404 error today, so no working official session service for SARKAR MD could be confirmed, and this guide links neither as a working service.
The tree of the readable fork contains a Dockerfile, a Procfile, app.json, package.json and a start script set built on PM2, which is file evidence of the run and deploy shapes the project prepared. The same tree contains no heroku.yml file, no render.yaml file and no start.sh file, and the template links in the README Deployment Options buttons point at a repository address that returns a 404 error today.
No. The repository metadata lists bandaheali.site as the project homepage, and that address did not load when checked for this guide, closing the connection without a response. It is listed in the links section of this guide for the record, with its status stated, and not as a working website.
No single license can be confirmed from the surviving records. The LICENSE file in the readable fork carries the MIT License text and the GitHub API detects MIT for that fork, but the status block of the same README names Apache and the license field of package.json reads ISC, and the original repository, whose own license file would settle the question, cannot be opened today. Readers should weigh all three signals before reusing the code.
Disclaimer
How this guide was prepared.
This article is based on the SARKAR MD records that could be opened on the last verified date: the public fork at miank/Sarkar-MD, read through the GitHub API and its raw files, including its README with the raw links behind its session and deployment buttons, its LICENSE file, package.json, app.json, config.js and its full repository tree, together with a check of the second fork under Sujaysujay52, whose README is only a short stub. On that date the original repository and the Bandaheali repository address both returned 404 errors, both session services returned 404 errors, and the project website did not load. A deployment tutorial link that circulates with summaries of this project could not be found anywhere in the README of any readable copy, so no tutorial is published in this guide. Where the records publish nothing, this guide says so instead of filling the gap.
AHMED X provides this article for educational and informational purposes only. AHMED X is not the developer or owner of SARKAR MD and does not claim any partnership or official affiliation with Sarkar Bandaheali or the project contributors.
AHMED X is not affiliated with, endorsed by, or sponsored by WhatsApp or Meta. WhatsApp is a trademark of its respective owner. Use unofficial WhatsApp automation at your own risk.
Keep Reading
More free WhatsApp bot guides from the AHMED X blog.
JAWAD-MD is an open source WhatsApp multi-device bot project by JawadTechX, with anti-delete, media downloaders, an AI chatbot, group tools, stickers and games. This guide covers the features its repository lists, how its 8 digit pairing code and Session ID work, and the deployment methods its README documents.
Read the guideKAMRAN-MD is a WhatsApp automation bot project from the KAMRAN-SMD GitHub repository. This guide explains what it is, which features its public documentation lists, how its pairing code works, and where to find the original project.
Read the guideA WhatsApp MD bot runs on your own number and answers commands in chats and groups. On AHMED X you deploy one free in minutes: get a session ID from a pair site, deploy, and your bot is live. No server, no coding.
Read the guideERFAN-MD is an independent website that offers a WhatsApp pairing code interface alongside guides on MD bots, commands and setup. This guide explains how its pairing process works, which feature categories its documentation covers, and what to check before linking a number.
Read the guidePick a bot from the AHMED X catalog and deploy it free in minutes. No server, no coding.
Browse Free Bots