AHMEDX
Guide

SIGMA MD WhatsApp Bot: Features, Session ID and Deployment Guide

SIGMA MD is a third party WhatsApp Multi Device bot project developed by Maher Zubair. The first fact a reader needs is where the code can still be read: the original repository, Maher-Zubair/SIGMA-MD, returns a 404 error on the web today, and the GitHub API reports that repository as access blocked. The full record survives in a public copy under the NeutronDroid account, an independent re-upload rather than a GitHub fork, whose package file reads version 1.4.9 and whose README and changelog match the last release the changelog records. A documentation mirror on GitLab also loads today. This guide is checked against the surviving copy: its README with its feature list and changelog, its app.json, its Setting.js, its sample configuration and its LICENSE file. One more present day fact shapes everything about using this bot: the developer domain the README sends readers to for a Session ID and for every deploy helper page, maher-zubair.tech, does not respond at all today.

By AHMED X · November 12, 2026 · Last verified November 12, 2026

About

What Is SIGMA MD WhatsApp Bot?

What the project is, who developed it, the present day state of its original repository, and which surviving records this guide is checked against.

SIGMA MD is a third party WhatsApp Multi Device bot project developed by Maher Zubair. The README banner reads, in the project own words, Welcome to the SIGMA-MD, Multi-Device WhatsApp Bot, Developed by Maher Zubair, and the package file describes it as a crazy WhatsApp bot by Maher-Zubair, with lib/client.js as its main file, a start script that runs it under PM2, and the WhiskeySockets Baileys package among its dependencies.

The original repository cannot be read today. The Maher-Zubair/SIGMA-MD address returns a 404 error on the web, the GitHub API reports the repository as access blocked, and the developer GitHub account address itself returns a 404 error through the API. Every route the README prints that points back at that account, including its fork button and its issues pages, is therefore dead. The record that survives in full is the public copy at NeutronDroid/SIGMA-MD-: GitHub does not mark it as a fork, so it is an independent re-upload of the project, last pushed in February 2024. Its package file reads version 1.4.9, which is exactly the latest release its changelog records, and a mirror of the documentation also loads on GitLab under the Bronnixx account. Every fact in this guide is checked against the NeutronDroid copy. Nothing from unrelated bots that share the SIGMA name is merged into this guide.

On licensing, the records inside the copy agree with each other. Its LICENSE file carries the Apache License 2.0 text, its package file names Apache-2.0 in its license field, and its README states that SIGMA-MD is made under the Apache-2.0 license. This guide names the Apache License 2.0 for the surviving copy, while noting that the README pairs that statement with the developer own warning against copying and re-uploading his bot, which readers should respect as his stated position.

Features

SIGMA MD WhatsApp Bot Features

The README publishes one feature list of ten entries, and its v1.4.9 changelog fills in what several of them mean. The cards below cover only that documented list, with the command count and the AI additions presented as the claims the project itself makes.

Meme Maker

The first entry in the README feature list, written there as Memes Maker. The README explains nothing further about how it behaves, so this guide records the documented name only.

Ban Protection

The README lists ban protection as a feature name and explains no mechanism for it anywhere in its documentation. Read it as a name on a list and nothing more: no feature in any bot can protect a WhatsApp account from bans, and the project own legal disclaimer accepts that a user who spams can be banned.

The Advertised Command Count

The README feature list advertises 450+ Commands. That figure is a claim the project makes about itself, presented here only as that claim: this guide does not present it as a counted fact. What can be checked is the changelog, which names the individual commands the v1.4.9 release added or fixed, and those names are the ones recorded in the commands section of this guide.

Logo Maker

The README list names a Huge Logo Maker Menu, and the changelog for v1.4.9 records logo commands being added and a logo maker plugin file sits in the copy tree. Huge is the project own wording, recorded as its presentation.

Multi Device Support

The README lists Multi-Device Supported as a feature: the bot connects through WhatsApp linked device authentication, by pairing code or QR, as its changelog describes.

Multiple Themes

The README lists Multi-Themes Supported. The copy carries a Themes folder of ready made theme files, a sample configuration that sets a theme value, and a changelog entry for a Theme command that changes the bot theme.

Artificial Intelligence Menu

The README lists an Artificial Intelligence Menu. The v1.4.9 changelog claims, in its own words, Added 11 AI, without naming the models, and the copy app.json carries an optional OPENAI_API_KEY setting, which shows that at least part of the AI side expects a user supplied key for an external service. Which AI features work today, and against which services, is not documented, so this guide claims nothing further.

Anime Commands

The README lists Massive Anime Commands, and the v1.4.9 changelog records Added Massive Anime. Massive is the project own adjective; the changelog names no individual anime commands beyond that entry.

Social Downloaders

The README lists Social Downloader Commands. The v1.4.9 changelog records fixes to the Insta, Tiktok and Facebook commands and the addition of a Spotify command for downloading Spotify songs, which are the downloader facts the surviving documentation supports.

Group Management

The README lists Group Management Commands. The changelog adds the detail that an Antiwords command was added to prevent bad words in groups, alongside group related fixes to the welcome, goodbye and antibot commands.

Commands

SIGMA MD Commands Named in the Changelog

The surviving README publishes no command table of its own. Every command below is named in the v1.4.9 changelog of the copy, grouped by purpose, with the changelog own description of what it does. The default prefix in the copy files is a dot, and the changelog records a setprefix command for changing it.

Group and Information

gc, to get the full details of a group. github, to look up GitHub users. category, to get all command categories. Together with the help command the changelog records being fixed, these are the discovery commands a new user meets first.

Behaviour Switches

typing turns automatic typing on or off. online controls the always online state. read controls automatic message reading. recording controls automatic recording. reaction controls automatic reactions. stsview controls automatic status viewing, stssaver automatically downloads statuses, and levelup controls automatic level up messages.

Media and Fun

spotify downloads Spotify songs. lyrics gets the lyrics of a song. calc performs simple math operations. tempmail generates temporary mail and gets its information. npm1 gets information about npm packages. insult, flirt and lines send their messages by mention or reply, and wamod downloads modified WhatsApp applications. The changelog also names afk and teddy commands.

Protection and Plugins

antiwords prevents bad words in groups, matching the ANTI_BAD_WORDS setting in the copy configuration files. plugin lists the external plugins, renamed to allplugins in the same changelog entry that records it. The README deployment steps point readers at an external plugins repository on the developer account, which returns a 404 error today like the rest of that account.

Session ID

How to Get a SIGMA MD Session ID

The surviving documentation does publish a session address: step 3 of the README deployment list and the SESSION_ID description inside app.json both point at sessions.maher-zubair.tech. That whole developer domain does not respond today, so no working official session service for SIGMA MD could be confirmed. This section records the documented route, its present day condition, and the authentication facts the changelog proves.

01

Start From the Surviving Copy README

Open the NeutronDroid/SIGMA-MD- copy and find its deployment methods list. Step 3 of that list is headed Get Your SESSION ID, and it holds the only session address the project publishes.

02

The Documented Session Address Does Not Respond

The README link and the app.json SESSION_ID description both give the same address, sessions.maher-zubair.tech. That address was opened again for this guide and the connection fails: the maher-zubair.tech domain does not respond at all today, at its root or at any of the paths the README prints. This guide links it for the record only, not as a working service.

03

Pairing Code Support: Added in v1.4.9

What the changelog proves about authentication is timing and method: the v1.4.9 release of 16 February 2024 records Added Pair Code For Session ID, Added New Session ID For Bot and Added New Qr. So the project documents three authentication pieces: a pairing code route, a Session ID the bot consumes, and QR authentication.

04

The Pairing Flow the Project Was Built For

Behind a pair code service of this kind, the flow is: enter your WhatsApp number with its country code on the service, 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. For QR, the same Linked Devices screen scans the code the service displays. This guide describes the flow because the changelog documents the methods, while stating plainly that the project own service for them is unreachable today.

05

Where the Session ID Goes

The bot consumes the value through configuration: app.json lists SESSION_ID with a description telling the user to put the Session ID there and pointing back at the session address, and Setting.js reads SESSION_ID from the environment as the session name the client uses. Keep any working session value private, because anyone holding it may be able to access the WhatsApp session it came from.

06

Avoid Unrelated Session Generators

With the original repository blocked and the documented session domain down, any unrelated website using the SIGMA 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

How to Deploy SIGMA MD WhatsApp Bot

The README deployment list names four routes: Heroku, Replit, Railway and GitHub Codespaces, each behind a helper page on the developer domain that does not respond today. This guide presents deployment at the level the surviving files prove: the steps the README lists, the configuration files the copy ships for each route, and the MongoDB requirement that gates all of them.

01

Star and Fork: The README First Steps Point at a Blocked Repository

Steps 1 and 2 of the README list are to star the repository and fork it, and both links point at the Maher-Zubair account, which cannot be opened today. In practice the readable starting point is the NeutronDroid copy itself. Expect the documentation of a project in this state to contain dead routes, as its session step already shows.

02

Get a Session ID

Step 3 of the README list is the session step covered in the session section of this guide: the documented address is on a domain that does not respond today, so no working official route could be confirmed.

03

MongoDB Is Required, in the README Own Words

Step 4 sends the reader to MongoDB Atlas to get a database URL, and the README repeats the requirement in its strongest lines: Strictly, use your own MongoDB key; Strictly, do not give your or use someone else MongoDB Url, otherwise you both will get issues; Strictly, without MongoDB your bot will not run. Setting.js repeats the same warning beside the setting that reads the MONGODB_URI environment value. There is no optional reading of this: a SIGMA MD deployment needs its own MongoDB URL, and that URL is a credential to keep private.

04

Heroku: The app.json in the Copy

The README Heroku helper page sits on the dead developer domain. What survives in the copy is app.json: it defines the Heroku shape directly, with a container stack, a single worker formation, a heroku-postgresql addon, and the environment the app asks for, including SESSION_ID, MONGODB_URI, PREFIX, OWNER_NAME, OWNER_NUMBER and the HEROKU_API_KEY and HEROKU_APP_NAME pair some SIGMA MD features expect. That is the extent of what the files prove.

05

Replit: Files Present in the Copy

The README Replit helper page is on the dead domain too. The copy ships a .replit file and a replit.nix file, which is file evidence that a Replit route was prepared by the project. This guide publishes no Replit procedure beyond what those files show.

06

Railway: A Listed Route With No File Behind It

Railway appears in the README list with its own helper page on the dead domain. Checked against the tree of the surviving copy, there is no Railway configuration file in it: the deployment files the copy carries are app.json, heroku.yml and the .replit pair. Any Railway procedure for SIGMA MD therefore rests on the reader own platform knowledge, not on project files this guide could check.

07

GitHub Codespaces: A Development Environment

The fourth listed route, behind the same dead domain, is GitHub Codespaces. Codespaces is a cloud development environment for working on code; the README lists it as a way to run the bot, but a development environment should not be assumed to provide uninterrupted production hosting.

08

Run From the Package Scripts

However it is hosted, the copy package file defines the run method: its start script runs lib/client.js under PM2 with the process name SIGMA-MD, after dependencies are installed and the SESSION_ID and MONGODB_URI values are in place.

Configuration

SIGMA MD Configuration Settings

The settings below are the ones the surviving copy actually carries, checked across its app.json, its Setting.js and its sample-config.env. Follow the exact names the files use and replace every shipped example value with your own.

SESSION_ID

The authentication setting. app.json describes it as the place to put your Session ID and points at the session address on the developer domain, and Setting.js reads it as the session name for the client. That domain does not respond today, as the session section of this guide records.

MONGODB_URI

The database setting, and the one the documentation guards most heavily. app.json describes it as your own MongoDB key and repeats that the bot will not run without a MongoDB URL, and Setting.js reads it into the bot global database value with the same warning in a comment. Never share this URL and never use someone else URL.

PREFIX

The command prefix. Three files in the copy agree on its default: app.json ships PREFIX with a dot, the sample configuration sets PREFIX to a dot, and Setting.js reads PREFIX with a dot as the fallback handler. The changelog records a setprefix command for changing it.

OWNER_NAME and OWNER_NUMBER

The owner identity settings in app.json and the sample configuration. They ship with the developer own values written in, and every deployer replaces the number with their own. Never use a number you find inside a public repository as if it were yours to claim.

WORKTYPE and THEME

WORKTYPE chooses whether the bot answers everyone or only its owner: app.json describes public and private in those terms and ships public, and the sample configuration agrees. THEME selects the bot theme; the sample configuration sets it to SIGMA_MD, one of the theme files the copy carries in its Themes folder.

Behaviour Values in the Sample Configuration

The sample-config.env file shows the shape of a working configuration: AUTO_REACTION, READ_MESSAGE, LEVEL_UP_MESSAGE and WELCOME_MESSAGE switches, a WARN_COUNT value, DISABLE_PM for turning the bot off in private chats, and ANTI_BAD_WORDS and ANTILINK_VALUES lists that the owner edits to their own needs.

Official Links

SIGMA MD Official Links

The resources checked for this guide: the surviving copy and its README, the blocked original, the GitLab mirror, the developer packages on npm, and the documented session address that no longer responds, each with its check result stated honestly.

SIGMA MD GitHub Repository (Surviving Copy)

The NeutronDroid/SIGMA-MD- repository, an independent re-upload of the project rather than a GitHub fork. It carries the full README with its feature list and v1.4.9 changelog, app.json, Setting.js, the sample configuration and the LICENSE file this guide verified against.

https://github.com/NeutronDroid/SIGMA-MD-

Original SIGMA MD Repository (Blocked)

The Maher-Zubair/SIGMA-MD address the README badges and fork button point at. It returns a 404 error on the web today and the GitHub API reports the repository as access blocked. Listed for the record, not as a working source.

https://github.com/Maher-Zubair/SIGMA-MD

SIGMA MD Documentation Mirror on GitLab

The Bronnixx/SIGMA-MD mirror on GitLab. It loads today and carries a copy of the project documentation.

https://gitlab.com/Bronnixx/SIGMA-MD

Maher Zubair Baileys Package on npm

The maher-zubair-baileys package the project side published on npm. Its registry record exists today. It is the developer own Baileys package, separate from the WhiskeySockets Baileys release the bot package file depends on.

https://www.npmjs.com/package/maher-zubair-baileys

SIGMA MD YouTube Downloader Package on npm

The sigma-md-yts package published for the project on npm. Its registry record exists today.

https://www.npmjs.com/package/sigma-md-yts

SIGMA MD Session Website (Offline)

The sessions.maher-zubair.tech address the README deployment list and the app.json SESSION_ID description both publish. The developer domain does not respond at all today, checked for this guide, and the address is listed for the record, not as a working service.

https://sessions.maher-zubair.tech

MongoDB

The MongoDB site the README sends readers to for the database account and connection URL this bot requires. The site loads today; the requirement itself is documented in the configuration section of this guide.

https://www.mongodb.com/

Safety

Is SIGMA MD WhatsApp Bot Safe?

The warnings the project prints about itself, the credential precautions its documentation states in the strongest terms, and the risks created by its blocked original repository and dead session domain.

SIGMA MD is an unofficial third party bot, and its README legal disclaimer speaks plainly: the bot is for fun and educational purpose, and the developer will not be responsible if you spam and get banned. Take that at face value. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect, and the feature list entry called ban protection changes none of that: it is a name in the README with no documented mechanism, and no feature in any bot can promise protection from WhatsApp bans. 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 blocked, the developer GitHub account cannot be opened, and the domain that hosted the project session website and every deploy helper page does not respond. 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 SIGMA MD session page as unverified.

Protect the two credentials this bot runs on. The documentation is unusually direct about the MongoDB URL: use your own, never share it, never use someone else, and understand that the bot will not run without it. The same care applies to your Session ID, which app.json and Setting.js show the bot consuming directly. The configuration files in the surviving copy carry shipped developer values, including an owner number, and those must be replaced with your own before any run. On licensing, the LICENSE file in the copy carries the Apache License 2.0 text, the package file names Apache-2.0, and the README states the same license, so the copy records agree.

Alternatives

Free MD Bots You Can Deploy on AHMED X

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

ASTRA X

WhatsApp MD Bot

Advanced AI-first MD bot with dual AI engines, media downloaders and deep group management.

Geston-MD

Geston-MD

WhatsApp MD Bot

Lightning-fast Baileys multi-device bot with AI chat, group protection and replies in many languages.

CELESTIA

CELESTIA

WhatsApp MD Bot

A polished multi-device WhatsApp bot with a large command library, AI chat and safe group tools.

TOXIC-MD

TOXIC-MD

WhatsApp MD Bot

Lightning-fast WhatsApp bot built on Baileys, made for speed and everyday automation.

SUKUNA-MD

SUKUNA-MD

WhatsApp MD Bot

A modular WhatsApp MD bot with group administration, media tools, protection engines and AI voice replies.

Levanter

Levanter

WhatsApp MD Bot

Multi-device WhatsApp bot packed with group protection, AI chat and a plugin system.

View all bots in the catalog

FAQ

SIGMA MD FAQs

Short answers to the questions readers ask most about SIGMA MD.

SIGMA MD is a third party WhatsApp Multi Device bot project developed by Maher Zubair and built on the Baileys library. Its README documents a feature list covering a meme maker, a logo maker menu, multi device support, multiple themes, an AI menu, anime commands, social downloaders and group management, and its changelog names the individual commands of its v1.4.9 release.

Maher Zubair. The README banner credits him as the developer, the package file gives its author as Maher-Zubair and describes the bot as his, and the sample configuration and app.json carry his name as the shipped owner name.

No. The Maher-Zubair/SIGMA-MD address returns a 404 error on the web, the GitHub API reports the repository as access blocked, and the developer account address itself returns a 404 error through the API. The full record survives in the public re-upload at NeutronDroid/SIGMA-MD-, whose package file reads version 1.4.9, and in a documentation mirror on GitLab that loads today.

The documented route is step 3 of the README deployment list, which points at sessions.maher-zubair.tech, the same address the app.json SESSION_ID description prints. That developer domain does not respond at all today, so no working official session service for SIGMA MD could be confirmed, and this guide links the address for the record only.

Yes, without exception in its own documentation. The README states strictly that without MongoDB your bot will not run, Setting.js repeats the warning beside the MONGODB_URI setting, and app.json describes the same setting as your own MongoDB key. You must create your own database and keep its URL private.

The README lists Heroku, Replit, Railway and GitHub Codespaces, each behind a helper page on the developer domain that does not respond today. Of the four, the surviving copy carries files for two: app.json for the Heroku shape and a .replit and replit.nix pair for Replit. No Railway configuration file exists in the copy tree.

A dot. app.json ships PREFIX with a dot, the sample configuration sets PREFIX to a dot, and Setting.js reads PREFIX with a dot as its fallback. The v1.4.9 changelog records a setprefix command for changing it.

The package file of the NeutronDroid copy reads version 1.4.9, which matches the latest release its changelog records, dated 16 February 2024 in the changelog itself. The copy was last pushed in the same month, so the surviving record is a consistent snapshot of that release.

The Apache License 2.0, on the evidence of the surviving copy: its LICENSE file carries the Apache License 2.0 text, its package file names Apache-2.0, and its README states the project is made under the Apache-2.0 license. The README pairs that with the developer own warning against copying and re-uploading, which readers should respect as his stated position.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the SIGMA MD records that could be opened on the last verified date: the public copy at NeutronDroid/SIGMA-MD-, read through the GitHub API and its raw files, including its README with its feature list and full v1.4.9 changelog, its LICENSE file, package.json, app.json, Setting.js, sample-config.env and its repository tree, together with checks of the original repository address, the developer account, the GitLab mirror, the npm registry records of the two project packages, and the developer domain. On that date the original repository returned a 404 error on the web with the API reporting it as access blocked, the GitLab mirror loaded, and maher-zubair.tech did not respond at its root, at its session subdomain or at its deploy helper paths. One correction to earlier summaries of this project matters: the surviving README does publish a session website address, in its deployment list and again inside app.json, and this guide names it and states its condition rather than saying none was published. 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 SIGMA MD and does not claim any partnership or official affiliation with Maher Zubair 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

Related WhatsApp Bot Guides

More free WhatsApp bot guides from the AHMED X blog.

Guide

SILVA MD WhatsApp Bot: Features, Session ID and Deployment Guide

SILVA MD is a third party WhatsApp Multi Device bot project from Silva Tech Inc, published in the open at github.com/SilvaTechB/silva-md-bot and actively maintained. Its README documents an AI assistant called Agent v2 backed by the ch.at service, a protection suite covering calls, deleted messages, links, view once media and group abuse, media downloaders, group management, games and a set of character themes. The repository homepage names its session selector site, which loads today and is where the README session flow begins, and the README recommends the project own Silva Host platform for deployment. This guide is checked against the repository itself: its README, package.json, LICENSE file and repository tree, together with the session and hosting addresses the README prints. Of those addresses, one documented route has broken since the README was written: the fork checker page the Heroku method depends on returns a 404 error today, and the TalkDrove sharing page did not load when checked.

Read the guide
Guide

What Is SUBZERO MD WhatsApp Bot?

SUBZERO MD is a third party WhatsApp Multi Device bot project by Darrell Mucheri, known online as Mr Frank, built with JavaScript and presented by its README as version 7. Its GitHub repository is live and links a working session service that offers both pair code and QR code login. One caution runs through this guide: the README itself publishes no feature catalogue and no command list, so the feature descriptions in circulation come from the developer project websites, and this guide keeps those two records separate throughout.

Read the guide
Guide

SUHAIL MD WhatsApp Bot: Features, Session ID and Deployment Guide

SUHAIL MD is an older third party WhatsApp Multi Device bot project from the Suhail Tech Info name, built on the Baileys library and designed around entertainment and interactive games. The plain facts first: the original GitHub repository cannot be opened today, the GitHub API reports its access as blocked, and the project appears no longer maintained, with the developer channel having directed users to a newer project called Suhail X, whose repository is also blocked on GitHub today. Everything in this guide is therefore checked against a publicly accessible copy of the repository, reu12th/Suhail-Md-Railway, which preserves the README and the project files, and this guide covers the original SUHAIL MD only, not SUHAIL MD V2 and not Suhail X.

Read the guide
Guide

SULA MD WhatsApp Bot: Features, Pairing Code and Deployment Guide

SULA MD is a third party WhatsApp Multi Device bot project by Sulaksha Madara, and two different things share its name. The first is the GitHub project: the repository that survives today under the developer account holds the application files, sula.js, settings.js, package.json, app.json and an Apache License, but no README at all. The second is the newer SULA OFC web platform at sulaofc.store, which offers cloud bot deployment through pair code connection and advertises its own feature set. The README that documented pairing and deployment buttons for the GitHub project lived on a second repository address, SULA-MD-NEW/SULA-MD, which returns a 404 error today. This guide keeps the repository and the platform separate from the first line to the last, exactly because mixing them produces wrong instructions.

Read the guide

Deploy Your Own Free WhatsApp Bot Today

Pick a bot from the AHMED X catalog and deploy it free in minutes. No server, no coding.

Browse Free Bots