HoneyPot

DO NOT SEND MESSAGES HERE
This channel is used to detect automated accounts.
Any message sent here triggers an automatic sanction (Softban).

42 accounts flagged

Message #honeypot

RaidProtect's HoneyPot (or trap channel) is an anti-spam feature: a channel where no one should write. Since real members know to stay away from it, the only ones who post there are hacked accounts or spam bots: RaidProtect sanctions them automatically.

info

You already have ScamLens by default. The ScamLens anti-scam is active on your server with no configuration at all: it specializes in scam images, detecting them, deleting them and sanctioning the compromised account with very high reliability. For image-based scams, ScamLens is more than enough on its own. The HoneyPot is mainly useful if you want maximum security and to block the other types of spam: link spam, text raids, bots.

❓ How does it work?

When you enable the HoneyPot, RaidProtect creates a text channel at the very top of your server, with a clear, randomly picked name. This channel has three characteristics:

• Anyone can write in it, including members who have not yet passed the captcha and those who have the Jail role. This is intentional: a hacked account or a bot must not be able to avoid the trap.
• A warning message ("DO NOT SEND A MESSAGE HERE") is posted when the channel is created, with a "Translate" button so everyone can read it in their own language.
• A flagged accounts counter appears as a button next to "Translate" as soon as the first account is caught.

As soon as a member posts in this channel:

• RaidProtect applies the sanction you have chosen (ban, softban, kick, timeout, jail or mute), without sending them a private message.
• The messages sent by this member in the past 10 minutes are deleted across the whole server, to stop the spam if it has already spread to other channels.
• The action is added to the auto-moderation logs (reason: Spam via compromised user account).

If you chose a delay before sanction, the member first gets a chance to say it was a mistake.

🛠️ Setting up the HoneyPot

1. Run the /settings command.
2. Open the "Protection" tab.
3. Click "Configure" next to "HoneyPot".
4. Click "Enable" at the top right: RaidProtect creates the channel, sets up the permissions and posts the warning message.

HoneyPot configuration
The HoneyPot is a trap channel visible and writable by all members (including those holding the Jail role or the captcha verification role). Any member who sends a message in it is automatically sanctioned by RaidProtect.

The channel is created at the very top of your server and a warning message is posted in it on creation (with a translate button).

---

HoneyPot channel

#ne-pas-ecrire

---

Applied sanction

Softban

Duration

1 day

Delay before sanctionWith a delay, the message is removed and the member is mentioned with a button to say it was a mistake. If they don't click in time, the sanction is applied. The same message posted in another channel, before or during the delay, is sanctioned immediately.

Immediate sanction

---

Ignored members

Nobody (except non-moderable members)

---

Support ServerDocumentation

Once the channel is created, you can:

• Regenerate channel (button next to "HoneyPot channel"): deletes the old channel and creates a new one, with a new name. Useful if you suspect a member has shared the trap channel's name to help other accounts avoid it.
• Disable (switch at the top right): deletes the channel and turns off the feature.

Required permissions

RaidProtect needs the Manage Channels and Ban Members permissions. Without them, an error box is displayed and the buttons stay grayed out.

Choose the sanction

By default, the HoneyPot applies a Softban. Several sanctions are available in the "Applied sanction" selector:

Sanction	Effect	Availability
Ban	Removes the member from the server and deletes their recent messages. Temporary (1 day by default).	Free
Softban	Bans then unbans: deletes the messages, but the member can come back	Free
Kick	Removes the member, who can rejoin freely	Premium
Timeout	Prevents the member from speaking for a chosen time (max 28 days)	Premium
Jail	Assigns the Jail role configured on your server	Premium
Mute	Assigns the Mute role configured on your server	Premium

For sanctions with a duration (Ban, Timeout, Jail, Mute), choose a duration in the "Duration" selector (1 day by default), or "Custom value" to enter your own (for example 5m, 1h, 2d; minimum 1 minute). The selector is grayed out for Softban and Kick, which have no duration.

The selector's presets follow the sanction:

Sanction	Presets offered
Ban	Permanent, 1 day, 7 days, 30 days
Jail	Permanent, 1 hour, 1 day, 7 days
Mute	5 minutes, 1 hour, 1 day, 7 days
Timeout	5 minutes, 1 hour, 1 day, 28 days

Ban and Jail can be permanent: the sanction does not lift by itself. When changing sanctions, the chosen duration is kept if it remains possible (a permanent one does not carry over to a Timeout or a Mute, and a Timeout stays under 28 days).

tip

The Softban is a good compromise: it cleans up the messages and removes the hacked account, but the legitimate owner can come back once their account is secured.

info

Only Ban and Softban let Discord natively delete the hacked account's messages everywhere on the server in one go. For the other sanctions (Kick, Timeout, Jail, Mute), RaidProtect deletes the messages itself: they are reserved for Premium servers.

info

• A Jail or a Mute without a configured role becomes a Timeout. The selector indicates it below the sanction.
• If your server loses Premium, a Premium sanction automatically goes back to Softban on the next trigger.

Delay before sanction

A good-faith member may write in the HoneyPot by mistake. The delay before sanction gives them time to report it before being sanctioned.

1. Run the /settings command.
2. Open the "Protection" tab.
3. Click "Configure" next to "HoneyPot".
4. In "Delay before sanction", choose "Immediate sanction" (default) or "Ask first, sanction after" 30 seconds, 1 minute, 2 minutes or 5 minutes.

With a delay:

• the message is removed and the member is mentioned in the trap channel, with the "It was a mistake" button;
• only this member can click the button. If they click in time, no sanction is applied;
• without a click before the end of the delay, the sanction applies.

info

A spam bot generally posts the same text everywhere. An account that posts the same message elsewhere is sanctioned right away, without waiting.

Ignored members

You can choose who is not sanctioned when a message is posted in the HoneyPot, in the "Ignored members" selector:

• "Nobody (except non-moderable members)" (default): everyone gets sanctioned, even staff. Only members the bot cannot moderate (role higher than RaidProtect's) are automatically spared.
• "Staff (Admin / Manage Server / Manage Channels)": members with the Administrator, Manage Server or Manage Channels permission are not sanctioned.
• "Members ignored by Antispam": RaidProtect reuses the ignored roles and members of the Anti-spam. If this list is empty, members with the Administrator, Manage Server or Manage Messages permission are ignored.

info

In every case, RaidProtect never sanctions itself or other bots. Bots do not trigger the HoneyPot.

ℹ️ The /honeypot command

The /honeypot command directly opens the HoneyPot configuration screen, without going through /settings. It requires the Manage Server permission.

Use the command: /honeypot

🤝 HoneyPot and ScamLens, better together

RaidProtect already includes ScamLens, which analyzes images and deletes the ones that are known scams (crypto, fake giveaways, fake casino promotions).

The two work hand in hand:

• ScamLens runs first. If the image posted in the HoneyPot is already known, ScamLens is the one that deletes the message and sanctions the compromised account; the HoneyPot sanction is not applied on top.
• The HoneyPot takes over for everything else: new images not yet known, link spam, mass mentions, text raids, bots.
• Every new image caught by a HoneyPot enriches ScamLens, which can then block it across all protected servers.
• ScamLens follows your HoneyPot: as long as you give it no setting of its own, it applies your HoneyPot's sanction and duration.

ScamLens is already active by default on your server. Enabling the HoneyPot doesn't break anything: it simply complements what is already there, and it helps RaidProtect protect the whole community better.

Frequently asked questions

Is the HoneyPot useful if I already have ScamLens?

For image scams, ScamLens is more than enough: it is active by default and detects, deletes and sanctions them on its own. The HoneyPot is mainly useful for blocking the other types of spam, such as link spam, text raids and bots.

Which sanction does the HoneyPot apply?

A Softban by default. You can choose another sanction: Ban and Softban are free, while Kick, Timeout, Jail and Mute are reserved for Premium servers. The HoneyPot's Ban lasts 1 day by default, a duration you can change.

A member wrote in the HoneyPot by mistake, what can be done?

Enable the delay before sanction: the message is removed, the member is mentioned and has 30 seconds to 5 minutes to click "It was a mistake". If they click in time, they are not sanctioned. An account that posted the same message elsewhere, however, is sanctioned right away.

Are staff members sanctioned if they write in the HoneyPot?

It depends on the "Ignored members" option. By default, everyone is sanctioned, even staff. RaidProtect never sanctions itself, and bots never trigger the trap.

What happens to the messages of an account caught by the HoneyPot?

On top of the sanction, the messages sent by that member in the past 10 minutes are deleted across the whole server, to stop the spam if it has already spread to other channels.