Security

Honeypot

Automatically punish users who post in a honeypot trap channel.


Note:

Slash commands for this page

Set this up in Discord with /configure feature:Honeypot, or on the dashboard under Security › Honeypot.

Use the slash version of each command below. Prefix commands keep working until March 5, 2027. What is changing

  • ,honeypot → /honeypot

Overview

A honeypot is a decoy channel that automatically detects and punishes anyone who posts in it. It's designed to catch compromised accounts, selfbots, and spam bots that ignore channel permissions. When triggered, greed can ban, kick, softban or time out the offender, purge their recent messages, DM them that their account looks compromised, and forward what they posted to your logs. Everything here also works as a slash command (/honeypot) and from /configure.

Getting Started

Set up a honeypot channel to begin:

,honeypot setup [channel]

greed will create a channel named honeypot if you don't provide one. The bot must have MANAGE_CHANNELS, BAN_MEMBERS, KICK_MEMBERS, and MANAGE_MESSAGES permissions.

Warning:

The honeypot channel will have no permission overwrites by default. You must manually configure the channel to hide it from regular members using role-based visibility settings in Discord.

Configuration

Once set up, customize how the honeypot responds to violations.

See the current honeypot settings:

,honeypot config

Shows the trap channel, punishment action, message history purge days, log channel, status, and total caught count.

Choose how to punish offenders. Options: ban, kick, softban (ban then unban, which clears their recent messages), or timeout (one hour: it stays in place even if they leave and rejoin).

,honeypot action (action)

Default punishment is ban. The bot must have permission to perform the chosen action.

When banning or softbanning, automatically delete the offender's messages from the past N days (0-7).

,honeypot history (days)

Set to 0 to keep all messages. Discord supports purging up to 7 days of history.

Warning:

History purge only applies to ban and softban actions. Kicked users' messages are not deleted.

Direct honeypot hits to a log channel for audit purposes.

,honeypot logs [channel]

Omit the channel argument to disable logging. greed must have SEND_MESSAGES permission in the log channel.

Temporarily disable the honeypot without removing its configuration.

,honeypot disable
,honeypot enable

Arm another channel with the same settings.

,honeypot add [channel]

Limit: 1 trap channel on the free plan, 5 with Server Premium. Spreading a few trap channels around the channel list catches more spam bots.

Turn individual behaviours on or off.

,honeypot option (dm|invite|forward|rename) (on|off)
OptionDefaultWhat it does
dmonDMs the caught user that their account looks compromised and how to secure it: sent before they're removed, so it always arrives. If they were banned and your appeals are open, the DM has an Appeal button.
inviteoffAdds a one-use, 7-day Rejoin link to the DM after a kick or softban, so a real member can come back once they've secured their account.
forwardonQuotes what they posted (and counts attachments) in the honeypot log.
renameoffRenames the trap channel every day from a list of ordinary-looking names, so spam bots can't learn to skip it.

Remove one trap channel, or the whole honeypot. Channels themselves are left intact.

,honeypot remove [channel]

Use the delete alias as shorthand: ,honeypot delete. Deleting a trap channel in Discord removes it from the honeypot automatically.

Tip:

When someone the honeypot banned submits an appeal, your review channel shows a Caught by the honeypot card with when it happened and what they posted: most honeypot catches are hacked accounts, so this makes the decision quick.

Incident Log

Every security action recorded by the bot: including honeypot triggers: is logged as a security incident. Administrators can review, search, and resolve incidents.

View all security incidents for your server.

,incidents list

Incidents are paginated; react to navigate. Status indicators show whether each incident is active or resolved.

Inspect a specific incident by ID.

,incidents view (id)

Shows incident type, module, status, detection details, and all recorded events with timestamps and actions taken.

Find incidents by user ID, keyword, or module.

,incidents search (query)

Returns up to 50 matching incidents, paginated.

Mark an incident as resolved.

,incidents resolve (id) [reason]

A reason is optional and not stored; it's only for your reference at resolution time. Active incidents show a resolve button when viewed.

Troubleshooting

Note:

Honeypots require the offender to post a message in the channel. If a member can see the channel but doesn't send a message, they won't trigger the trap. Use Discord's permission system to hide the channel from regular members.

Warning:

greed's role must be above the offender's highest role to apply the punishment. If the bot cannot ban or kick a user, the action silently fails and the incident is still logged.

Warning:

Softban (ban + unban) removes the user from the server but does not prevent them from rejoining immediately. Use regular ban if you want persistent blocking.

Note:

Incidents are retained in the database indefinitely. The incident log is an audit trail and cannot be deleted.