TOXIC-MD

Toxic-MD is an open-source WhatsApp Multi-Device bot built with the Baileys library. It combines WhatsApp automation, AI-powered chat, group moderation, media tools, utility commands, and customizable bot settings in one project.

If you want to automate repetitive WhatsApp tasks, manage group activity, create stickers, use supported media tools, or experiment with custom commands, Toxic-MD provides a flexible platform to explore these features.

You can generate a WhatsApp pairing session through the official Toxic-MD pairing page and use the deployment options on AHMED X to launch your bot. This guide covers its documented features, pairing process, command categories, setup, troubleshooting, and safety considerations.

Compare it with every other bot in the bot catalog, or read the full deployment guide before you start.

Toxic-MD documents a wide set of automatic behaviors that run without you sending a command each time. The exact behavior depends on the bot settings and the version you deploy.

The project also documents AI-powered chat using Groq and Llama integrations, which can provide automated responses through supported AI services, depending on the configuration and API access the deployed version requires. AI responses may be inaccurate, and external AI services may have their own usage limits or costs, so check the project's current documentation before enabling this feature.

Group control is a central part of Toxic-MD. Its README documents the protection and moderation features below. Not every option necessarily runs by default, so review the current project configuration, and remember the bot needs suitable group permissions for administrative actions.

Configure moderation carefully so legitimate links and messages are not removed unintentionally, especially in communities with different language or content requirements. Anti-delete and view-once recovery are not a guarantee that every message or media file can always be recovered.

Service availability for downloads can change, and not every URL or media type is guaranteed to work. Use only media you have permission to download and share.

The project's v1.1.1 notes describe a CRM store that uses local JSON storage and automatically uses PostgreSQL when DATABASE_URL is configured, together with improved linked-device ID mapping and a larger message cache (MESSAGE_CACHE_LIMIT = 50000). These are version-specific implementation details, so verify that the deployed version includes them before relying on them.

Toxic-MD organizes its commands across automation, moderation, media, utilities, entertainment, and system management. The exact commands and aliases depend on the current version and configuration, so use the bot's menu or help command to discover what is available instead of relying on an unverified list. Some commands require owner privileges or administrator access in the group.

Toxic-MD uses configuration files and environment-based setup. For a self-hosted instance, the repository documents the session setting in the format shown below. Replace the example value with your own valid session credential, and never publish a real session value.

Depending on the version, other configuration controls the command prefix, language, operating mode, database connection, and optional integrations. If you deploy through AHMED X, use the fields actually provided by the deployment form rather than assuming every self-hosting option is available.

Developers who prefer self-hosting can use the official repository at github.com/xhclintohn/Toxic-MD. The general process is to prepare a compatible Node.js environment, obtain the source code, install dependencies, configure the session, and start the application using the documented commands. Installation details can change between versions, so follow the current README rather than assuming old commands still work.

Toxic-MD is a third-party WhatsApp automation project, not an official WhatsApp application. Its own repository warns that unofficial WhatsApp APIs may violate WhatsApp's terms and that use of the bot is the user's responsibility. No unofficial bot can guarantee that an account will never be restricted or banned, so use the project at your own discretion and keep this guidance in mind: