Skip to main content
The honeypot does two things, and the second one is the reason to set it up even if you never get raided.

The bait channel

A channel nobody should ever post in. Anything posted there is treated as proof the account is compromised, and it’s punished instantly.

Server-wide image scanning

Fingerprints every scam image it catches, then blocks that image everywhere — even when the scammers change the text around it.
The bait works because the accounts you’re trying to catch aren’t reading. A hijacked account running a scam script blasts its payload into every channel it can see — including this one, usually before it reaches the channels your members actually use. Requires Administrator.

​
Setting it up

That’s genuinely it. The first command creates the channel, locks it down, writes a warning topic and starts watching. The second turns on image scanning, which is where most of the ongoing value is.

​
Setup flags

softban is the default for a reason. It bans and immediately unbans, which wipes the account’s recent messages across the whole server but lets the real owner rejoin once they’ve recovered their account. ban is the right call if you’d rather they contact you first.

​
Why --warmer matters

An empty channel with no history looks suspicious to the scam and gets skipped by some scripts. With the warmer on, mira posts occasionally to keep it looking like a real, quiet channel. Leave it on unless you have a reason not to.

​
Punishment

Aliases: punishments, action, actions, punish, do.

​
Cleaning up their other messages

When someone trips the honeypot, their messages from the last N of history are deleted across the whole server. This is what actually stops the scam — the bait message is irrelevant, the twelve copies they’ve already posted in your real channels are the problem. 1h is a sensible default. Aliases: prune, purge.

​
Image scanning

Aliases: images, scanimages, sc, imgs. This is the part worth turning on regardless of whether you’re being raided. Every image the honeypot catches is fingerprinted with perceptual hashing, and from then on that image is blocked in every channel in your server — not just the bait channel.

​
Why perceptual hashing matters

A normal file hash changes if a single pixel changes, which makes it useless against scammers. Perceptual hashing fingerprints what the image looks like, so the same graphic still matches after it’s been:
  • Re-saved, re-compressed, or screenshotted
  • Resized or cropped slightly
  • Recoloured or watermarked
  • Wrapped in different text, a different link, or a different filename
Scam campaigns reuse the same handful of graphics for weeks and rotate everything around them. Catching the graphic once means catching every later variation of it automatically.

​
The workflow

1

Someone posts a scam image in the honeypot

They’re punished, their recent messages are purged, and the image is fingerprinted.
2

The same image is now blocked server-wide

Anyone posting it in any channel gets caught, including accounts that never touched the bait channel.
3

Add anything that slips through by hand

Reply to the offending message. Every image attached to it is fingerprinted and blocked from then on.
!honeypot blacklist add works on any message, not just honeypot ones. When a scam graphic gets posted in #general, replying to it with that command is the fastest way to make sure it never appears again — and it takes effect immediately for every channel.

​
Managing the blocklist

honeypot blacklist add works on a reply or a message link, and hashes every image attached to it. Use it when a scam graphic gets through — that exact image will never post again. Requires Manage Server for add/list/remove; Administrator to clear.

​
Other settings

honeypot message accepts a full script, so the channel topic message can be an embed or a container. honeypot disable deletes the channel and stops all monitoring.

​
Reviewing the configuration

Shows the channel, punishment, DM setting, booster setting, history window, scan state and blocklist size.

​
Command reference

Group aliases: honey, pot, hp.
Tell your staff the channel exists. The most common honeypot incident is a moderator posting “what’s this channel for” in it and immediately softbanning themselves.