AHMEDX
Guide

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

SUPUN MD is a third party WhatsApp Multi Device bot project by Mr. Supun Fernando, a developer from Sri Lanka who also works under the name Dark Shadow Modz. The first fact a reader needs is where the project can still be read: the original repository, mrsupunfernando12/SUPUN-MD, returns a 404 error today, and the developer GitHub account behind it returns a 404 error as well. The record survives in partial copies, one on GitLab under the Nadu-12 account and one on GitHub under the iam-dsmodz account, and in three developer pages that still load. The pages load, but every pairing service behind them returns a 404 error today, so this guide links no working session service for SUPUN MD. A security report covered in the safety section gives readers a second reason to check every dependency carefully before running anything connected to this project name.

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

About

What Is SUPUN MD WhatsApp Bot?

What the project is, who developed it, and where its record can still be read today now that the original repository and the developer GitHub account are both gone.

SUPUN MD is a third party WhatsApp Multi Device bot project by Mr. Supun Fernando, a developer from Sri Lanka. The README header preserved in the surviving copies presents it as a Multi Device WhatsApp bot developed by Dark Shadow Modz, the developer other name, and the README footer presents the release as SUPUN MD V3 and gives a release date of 18 January 2025 with a last updated date of 7 March 2025. The package file in the GitLab copy carries version 3.3.8, so the V3 presentation and the package version string are both reported here exactly as they stand.

The original repository, mrsupunfernando12/SUPUN-MD, cannot be read today. Its GitHub page returns a 404 error, the GitHub API reports it as not found, and the developer account page itself, github.com/mrsupunfernando12, also returns a 404 error. What survives is partial. A copy on GitLab under the Nadu-12 account carries the full README, a LICENSE file, app.json, package.json, settings.js and an index.js whose code is heavily obfuscated. A second copy on GitHub under the iam-dsmodz account carries a LICENSE file, app.json, package.json, settings.js, a supunmd.js file and a talkdrove.json file. Neither copy holds the full application tree the project once published, so every fact in this guide is checked against these copies and against the developer pages that still load, and where the copies publish nothing, this guide says so instead of filling the gap.

The developer pages are the living part of the record. The README sends readers to supun-md-web.vercel.app through a button labelled Deployment Methods, and that page loads today: it presents Mr. Supun Fernando, links his YouTube channel and his WhatsApp channel, and carries two buttons, one labelled Session ID and one labelled MD Deploy. Both destination pages also load today. What does not survive is everything behind them, as the session and deployment sections below record in detail.

The README itself is a presentation document, not a manual. Beyond the fork button, the deployment methods button and a sample Node.js workflow, it publishes no feature list, no command list, no configuration reference and no session instructions. Readers who meet detailed SUPUN MD feature or command lists elsewhere should know that none of them come from the project README this guide could check.

Features

SUPUN MD WhatsApp Bot Features

The README publishes no feature list at all, so the cards below cover only what the surviving files and the developer pages actually prove: the kind of application it is, how it connects, how it runs and how it is configured.

WhatsApp Multi Device Support

The README header presents SUPUN MD as a Multi Device WhatsApp bot, and the project is built to operate through a linked WhatsApp account rather than as a separate WhatsApp application. That linked account model is the whole basis of the project.

Built on Baileys

The package file in the GitLab copy declares its WhatsApp library under the WhiskeySockets Baileys package name. The dependency is written as an npm alias that resolves to a different package, asitha-baliyes-new, rather than to the official release, a detail the safety section of this guide returns to.

JavaScript and Node.js Application

The project is a JavaScript application. The package file in the GitLab copy names index.js as its main file and describes the project as a WhatsApp bot created using Node.js. The README sample workflow and both surviving copies agree on that shape.

Session ID Authentication

The app.json file in the surviving copies requires a single environment value named SESSION_ID, described in the file as the place to paste your SUPUN MD session. Authentication for this project is therefore a Session ID value supplied at deploy time, whatever route produced it.

Runs Under PM2

The start script in the package file runs the application under PM2, starting index.js with the process name supunmd, 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.

Settings File Configuration

Both surviving copies carry a settings.js file, and the GitLab copy also carries the application entry file beside it. The readable settings material is limited, and the main application file in the GitLab copy is obfuscated code, so this guide publishes no settings list it could not read plainly.

No Published Feature or Command List

This card exists to state a negative plainly. The README publishes no feature list, no command names, no command categories and no prefix, and no readable command reference survives in either copy. This guide invents none, and any SUPUN MD command list found elsewhere does not come from documentation this guide could check.

Session ID

How to Get a SUPUN MD Session ID

The documented route runs from the README to the developer web page, from the web page to a session page, and from the session page to three pairing services hosted on Render. Every page in that chain was opened again for this guide: the pages load, and all three pairing services return a 404 error, so the route is documented here together with its present day condition.

01

Start From the README Deployment Methods Button

The README preserved in the surviving copies carries one deployment entry point: a button labelled Deployment Methods that points to supun-md-web.vercel.app. There is no session link in the README itself, so every documented route to a SUPUN MD session starts at that developer page.

02

The Developer Web Page Loads Today

supun-md-web.vercel.app opens today and presents the developer, his YouTube channel and his WhatsApp channel. Its Session ID button points to supun-md-session.vercel.app and its MD Deploy button points to supun-md-deploy.vercel.app. Both of those pages also load today.

03

The Session Page Offers Three Pairing Services

The session page, titled SUPUN MD SESSION PAGE, offers three pairing options labelled PARING 01, PARING 02 and PARING 03. Behind them sit three separate services hosted on Render: supun-md-pair-8jld.onrender.com, supun-md-pair-mega.onrender.com and supun-md-v3-pair-34q3.onrender.com.

04

All Three Pairing Services Return 404 Today

Each of the three Render services was opened again for this guide, and each one returns a 404 error. The pairing backends the session page depends on are gone, so no working official pairing service for SUPUN MD could be confirmed, and this guide links none of the three as a working service.

05

Where the Session ID Goes

The project consumes the result as an environment value: app.json in the surviving copies lists SESSION_ID as its one required setting, with a description telling the user to paste the SUPUN MD session they obtained. Keep that value private, because anyone holding working session credentials may be able to access the WhatsApp session they came from.

06

Avoid Unrelated Session Generators

With the original repository gone and every documented pairing backend returning 404, any unrelated website using the SUPUN 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 SUPUN MD WhatsApp Bot

Deployment evidence for SUPUN MD comes from three places: the developer deploy page, which still loads but builds its prefilled routes on the gone repository; the app.json file in the surviving copies, which is shaped for a Heroku style deploy; and the manual Node.js flow the README sample workflow and the package scripts define.

01

Read the Repository Status First

Every route in this section runs into the same fact: the original repository at mrsupunfernando12/SUPUN-MD returns a 404 error today, and the developer GitHub account is gone with it. Routes that point at that address cannot be followed as written, and this guide presents them as records, not as working buttons.

02

The Developer Deploy Page Loads, Its Routes Point at a Gone Repository

supun-md-deploy.vercel.app, titled SUPUN MD DEPLOY, opens today. Its two prefilled routes are a Heroku template link and a Koyeb deployment link, and both are built on the original repository address that returns 404. The Koyeb link also presets a SESSION_ID value and a MONGODB value and names a Dockerfile, which tells a reader what that route expected, but it cannot deploy a repository that no longer opens. The page also carries generic links to other hosting dashboards, which are not project specific routes.

03

Heroku Shape: app.json

Both surviving copies carry an app.json file. It names the app SUPUN-MD, requires the SESSION_ID environment value, and declares the Heroku Node.js buildpack on the heroku-24 stack. That is the shape of a Heroku style deployment prepared in a file, and it matches the template route the deploy page advertises, but the template source repository is gone today.

04

Manual Flow From the README Workflow

The README publishes a sample Node.js CI workflow, and it is the only complete manual flow the documentation gives: Node.js 20, install dependencies with npm install, and start the application with npm start. Work from one of the surviving copies, review its files first, and expect the gaps recorded in this guide.

05

What npm start Actually Runs

The package file gives the start script a precise meaning: it launches index.js under PM2 with the process name supunmd and attaches to it, with stop and restart scripts beside it. A manual run therefore depends on the copy you downloaded being complete, and neither surviving copy holds the full application tree, so a clean start cannot be promised from them.

06

Configure the Session Before Starting

Whatever route you use, the application expects its SESSION_ID value to be present. Replace any shipped example or placeholder with your own session, obtained only through a route you can trace back to the developer, and never through an unrelated generator page.

Configuration

SUPUN MD Configuration and Project Files

The configuration evidence that survives is thin: one required environment value in app.json, a settings file in both copies, and a short list of files the copies actually hold. This section records exactly that and nothing more.

SESSION_ID

The only setting app.json lists, and it is required. Its description tells the user to paste the SUPUN MD session they obtained. Every run route depends on this one value being present and private.

MONGODB on the Koyeb Route Only

The prefilled Koyeb link on the developer deploy page presets a MONGODB value beside SESSION_ID. No surviving project file explains a database requirement, so this guide records the variable as something that one route expected, not as a documented project requirement.

settings.js

Both surviving copies carry a settings.js file, which is where this project keeps its editable settings. Because the copies are partial and the main application file in the GitLab copy is obfuscated, this guide publishes no list of individual settings it could not read plainly.

Files in the GitLab Copy

The copy at gitlab.com/Nadu-12/supun-md holds six files: README.md, LICENSE, app.json, package.json, settings.js and index.js. It holds no command file, no plugins folder and no session folder, whatever the full project once contained.

Files in the GitHub Copy

The copy at github.com/iam-dsmodz/SUPUN-MD holds a LICENSE file, app.json, package.json, settings.js, a supunmd.js file and a talkdrove.json deployment file. It is likewise partial, and its file set is not identical to the GitLab copy, so always follow the files inside the exact copy you downloaded.

Official Links

SUPUN MD Official Links

The resources checked for this guide: the two surviving partial copies, the developer pages that load, the pairing services that do not, the channels the README publishes, and the security report named in the safety section, each with its check result stated honestly.

SUPUN MD GitLab Copy

The copy at gitlab.com/Nadu-12/supun-md, which carries the full README text, the LICENSE file, app.json, package.json, settings.js and an obfuscated index.js. It is a copy, not the original repository, and it is the most complete record this guide could read.

https://gitlab.com/Nadu-12/supun-md

SUPUN MD GitHub Copy

The copy at github.com/iam-dsmodz/SUPUN-MD, carrying a LICENSE file, app.json, package.json, settings.js, supunmd.js and talkdrove.json. A partial copy under another account, listed because it corroborates the files the GitLab copy holds.

https://github.com/iam-dsmodz/SUPUN-MD

Original SUPUN MD Repository (Offline)

The mrsupunfernando12/SUPUN-MD address the README badges and fork button point at. It returns a 404 error today, and the developer account page returns a 404 error as well. Listed for the record, not as a working source.

https://github.com/mrsupunfernando12/SUPUN-MD

Developer Web Page

supun-md-web.vercel.app, the page the README Deployment Methods button points to. It loads today and carries the Session ID and MD Deploy buttons checked for this guide, together with the developer YouTube channel and WhatsApp channel links.

https://supun-md-web.vercel.app/

Session Page (Pairing Services Offline)

supun-md-session.vercel.app loads today and offers three pairing options, but all three Render services behind it return a 404 error. Listed so readers can see the documented route and its present day condition in one place.

https://supun-md-session.vercel.app/

Developer Deploy Page

supun-md-deploy.vercel.app loads today. Its prefilled Heroku and Koyeb routes are built on the original repository address, which returns a 404 error, so they cannot be followed as written.

https://supun-md-deploy.vercel.app/

Developer WhatsApp Channel

The WhatsApp channel the README links, presented there as the place to follow the developer and the project.

https://whatsapp.com/channel/0029VaXRYlrKwqSMF7Tswi38

Developer YouTube Channel

The YouTube channel the README and the developer web page both link, under the Dark Shadow name the developer also works by.

https://youtube.com/@darkshadow_zap

OX Research PhantomSub Report

The September 2026 OX Research report on the PhantomSub malicious npm campaign. Its affected packages table names the Baileys package published under the developer npm scope, as the safety section of this guide explains.

https://www.ox.security/blog/phantomsub-malicious-npm-campaign-secretly-adds-users-to-whatsapp-spam-channels/

Safety

Is SUPUN MD WhatsApp Bot Safe?

The precautions that apply to SUPUN MD, including the warning its own README prints, the dependency facts in the surviving package file, and the PhantomSub security report that names a Baileys package published under the developer npm scope.

SUPUN MD is an unofficial third party bot, and its README prints a warning of its own: the developers are not responsible for any inconvenience caused by your mistakes. Take the wider risk at face value as well. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect, and no setting 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.

The PhantomSub report. In September 2026, OX Research published its PhantomSub report on a malicious npm campaign built on modified Baileys packages that silently make a connected WhatsApp account follow spam channels. The affected packages table in that report names @mr-supun-fernando/supunmd-bail, a package published under the SUPUN MD developer npm scope and described on npm as a WhatsApp API modification by Supun Fernando, and the report records one of the channels promoted in that package README as a channel carrying the developer name. To be precise about what this does and does not prove: the flagged package is a separately published npm package, and its presence in the report is not proof that the SUPUN MD repository code itself is malicious. It is, however, a documented reason never to install that package, and a strong reason to review every dependency before connecting a WhatsApp account to anything published under this project name.

The surviving package file adds a second, quieter reason for the same caution. Its dependency list does not include the flagged package, which this guide verified directly, but its Baileys dependency is written as an npm alias that resolves the WhiskeySockets Baileys package name to a different third party package, asitha-baliyes-new. In plain terms, installing the project as shipped does not fetch the official Baileys release. That package is not named in the OX report, and this guide makes no claim about it beyond what the file shows, but any reader who runs this project should know which code their WhatsApp session will actually connect through, and the main application file in the GitLab copy is obfuscated code that cannot be reviewed by reading it.

Understand the present day state before connecting anything. The original repository and the developer GitHub account are gone, both surviving copies are partial, and every documented pairing backend returns a 404 error. A vacuum of this kind is exactly what fake session websites exploit. Only trust authentication links you can trace back to the developer pages themselves, treat every other SUPUN MD session page as unverified, and never share your Session ID in chats, screenshots or public forks.

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

SUPUN MD FAQs

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

SUPUN MD is a third party WhatsApp Multi Device bot project by Mr. Supun Fernando, a developer from Sri Lanka who also works under the name Dark Shadow Modz. Its README presents it as a Multi Device WhatsApp bot, its package file describes it as a WhatsApp bot created using Node.js, and its footer presents the release as SUPUN MD V3.

The project is by Mr. Supun Fernando. The README names him as creator, the developer web page presents him and links his YouTube channel and WhatsApp channel, and the README header credits Dark Shadow Modz as the developing name.

No. The mrsupunfernando12/SUPUN-MD address returns a 404 error today, and the developer account page itself returns a 404 error as well. What survives is partial: a copy on GitLab under Nadu-12 holding the README, LICENSE, app.json, package.json, settings.js and an obfuscated index.js, and a copy on GitHub under iam-dsmodz holding a LICENSE file, app.json, package.json, settings.js, supunmd.js and talkdrove.json.

The README publishes no feature list and no command list, and no readable command reference survives in either copy, so this guide publishes none. What the files prove is narrower: a Multi Device bot application in JavaScript, a Session ID environment value required by app.json, PM2 run scripts in the package file, and a settings.js file. Any detailed SUPUN MD feature or command list found elsewhere does not come from project documentation this guide could check.

The documented route is the developer web page that the README Deployment Methods button points to, and from there the session page it links. That session page loads today and offers three pairing options, but all three Render services behind it return a 404 error, so no working official pairing service for SUPUN MD could be confirmed, and this guide links none of them as a working service.

The developer deploy page loads today and offers prefilled Heroku and Koyeb routes, but both are built on the original repository address, which returns a 404 error, so they cannot be followed as written. The manual flow the README sample workflow gives is Node.js 20, npm install and npm start, and the package start script runs the application under PM2 with the process name supunmd.

The LICENSE file in both surviving copies carries the full text of the Apache License 2.0. Because the original repository cannot be opened, its own LICENSE file cannot be checked, so this guide reports the license exactly at that level: Apache License 2.0 is the license the surviving copies of the project carry.

PhantomSub is the name OX Research gave in September 2026 to a malicious npm campaign built on modified Baileys packages that silently make a connected WhatsApp account follow spam channels. The report affected packages table names @mr-supun-fernando/supunmd-bail, a Baileys modification published under the SUPUN MD developer npm scope. That package is separate from the repository code, and the surviving package file of the bot does not list it as a dependency, which this guide verified directly. The report is not proof that the repository itself is malicious, but the named package should never be installed, and every dependency of anything published under this project name should be reviewed before use.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the SUPUN MD records that could be opened on the last verified date: the GitLab copy at Nadu-12/supun-md, read in full, including its README, LICENSE file, app.json, package.json, settings.js and the opening of its obfuscated index.js; the GitHub copy at iam-dsmodz/SUPUN-MD and its file list; the developer web page, session page and deploy page, all three of which load; and the OX Research PhantomSub report. On that date the original repository and the developer GitHub account both returned 404 errors, all three pairing services behind the session page returned 404 errors, and both surviving copies proved to be partial, holding neither the full application tree nor any readable command reference. The developer personal WhatsApp number, which the project pages publish as a contact, is not reproduced 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 SUPUN MD and does not claim any partnership or official affiliation with Mr. Supun Fernando 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

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

VAJIRA MD is a third party WhatsApp Multi Device bot project by Vajira Rathnayaka, a developer from Sri Lanka who also works under the name Vajira T.D.D. The first fact a reader needs is the state of the record: every repository under the developer own accounts returns an access blocked notice from GitHub today, and the repository copy that carried the V9 README has been deleted outright. What survives is an older V7 README preserved in a public copy, a partial set of the project deployment files preserved in another, and a live Railway template that still names the developer and still requires a Session ID, while pointing at a repository nobody can open. This guide is checked against those surviving records, presents the V9 material only where a surviving file corroborates it, and says plainly where the documentation can no longer be rechecked at all.

Read the guide
Guide

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

VENOM MD is a third party WhatsApp Multi Device bot project published by Bryan Tech, and unlike many projects in this series its original GitHub repository, Bryanlover1/VENOM-MD, still opens today, so this guide is checked against the repository itself: its README read in raw form, its full file tree, its package file, its example environment file, its settings file, its Heroku configuration and its LICENSE file. Two findings shape everything about using this bot. The README itself states, in its own capital letters, that its pairing code route temporarily uses the Naruto MD pairing service, and both authentication services it links return a 404 error today. And the repository package file does not match the project it sits in: it names the package MADARA-MD and points at a main file the repository root does not contain. Both facts are recorded plainly in the sections below.

Read the guide
Guide

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

WASI MD is a third party WhatsApp Multi Device bot project by Itxxwasi, also presented as Mr Wasi, and the identifiable current project is WASI MD V7 in his own GitHub repository. The original repository is live and was read in full for this guide: its README documents the feature categories and command tables, its .env.example and config.js carry the settings, and its troubleshooting section describes QR authentication with a delete the session folder and rescan flow. The project publishes no pairing website for V7, and the developer separate session generator repository today links to a website that shows unrelated proxy content, so this guide links no WASI MD pairing page as a working service.

Read the guide
Guide

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

XBOT MD, written X BOT MD inside its repository, is a third party WhatsApp Multi Device bot project by Aswin Sparky. The original repository is live today under the renamed Aswin-Sparky account, with the older A-S-W-I-N-S-P-A-R-K-Y address redirecting to it, and this guide is checked against that repository directly: its README documents QR authentication and four deployment routes, and its session service was opened again for this guide and is working, asking visitors to sign in with GitHub and fork the repository before it offers QR pairing and a pair code option. A separate pairing project by the same developer exists only as source code to host yourself, and the README publishes no command list, so this guide publishes none.

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