What Honeypot Protection does
Honeypot Protection watches specific text channels that regular members have no reason to use. When a member sends a message in a monitored channel, AioBot treats it as a suspicious activity signal and applies the enforcement action you configured.
Typical uses include catching compromised accounts, spam bots, and raid accounts. Every trigger is recorded as a deduplicated incident, and AioBot never stores the triggering message content.
Before you begin
- A connected bot that can view the channels you want to monitor.
- Bot permissions that support your planned action: Manage Channels for channel management and Ban Members for ban, softban, and timeout enforcement.
- Premium on this server. Honeypot Protection is a Premium capability under the current plan policy.
Configure Honeypot Protection
- 1
Open Advanced Moderation > Honeypot Protection and enable the feature.
- 2
Select one or more existing text channels to monitor. Threads and forum posts are excluded, and channels the bot cannot view are not selectable.
- 3
Choose the enforcement action: Delete message, Timeout member, Kick member, Ban member, or Softban member, together with its timeout or message-history options.
- 4
Add exemptions for trusted roles or Discord user IDs. The server owner and members with administrator permissions are always exempt.
- 5
Save protection settings. Enabling live enforcement for the first time asks you to confirm.
Settings reference
| Option | What it does |
|---|---|
| Monitored channels | Messages in exactly these text channels trigger protection. Honeypot Protection requires Premium; Premium has no plan cap on monitored channels. |
| Delete message | Removes the triggering message without acting on the member. |
| Timeout member | Temporarily removes the member's ability to send messages. Choose a preset from 5 minutes to 7 days, or a custom duration from 1 to 40,320 minutes. |
| Kick member | Removes the member from the server; they can rejoin with a new invite. |
| Ban member | Permanently removes the member, optionally deleting recent message history (choose up to 7 days). |
| Softban member | Bans and then unbans the member with a one-use rejoin invite, optionally sent by direct message with an editable notice of up to 1,000 characters. |
| Exempt roles | Members with these roles never trigger enforcement. Managed roles are not listed. |
| Exempt user IDs | Up to 100 Discord user IDs, one per line, validated before saving. |
| Honeypot message | A separate draft-and-publish flow for a warning notice in one monitored channel. Embed format is available whenever the feature is enabled; Components V2 requires Premium. |
| Live counters | The published notice supports {honeypot.triggers}, {honeypot.actions}, {honeypot.deleted}, {honeypot.timeouts}, {honeypot.kicks}, {honeypot.bans}, {honeypot.softbans}, {honeypot.failed}, {server.name}, and {server.member_count}. AioBot refreshes published counters and supported variables automatically on the same message. |
| Statistics | Durable counters for triggers, actions, deletions, failures, timeouts, kicks, bans, and softbans. Resetting requires a typed confirmation and preserves incident history. |
| Recent incidents | Deduplicated enforcement history showing the action, member, channel, and time. Failed actions are flagged so you can check the bot connection and permissions. |
| Protection status | The header status shows Healthy, Pending save, Disabled, Misconfigured, Warning, or Bot check overdue, so you can confirm the bot is enforcing. |
Choose the trap carefully
Verify it is working
- Save the settings and confirm the header status becomes Healthy after the bot check completes.
- From a non-exempt test account, send one message in a monitored channel and confirm the configured action appears under Recent incidents.
- If you published a notice, confirm its counters increased after the test trigger.