🍯 Bleed Honeypot Protection

Bleed’s Honeypot system creates a bait channel designed to identify and automatically punish obvious spam bots, raid accounts, or malicious users who interact with a channel they should have no legitimate reason to use.

Because honeypots can automatically trigger punishment, configuration should remain strictly Owner-only.

🍯 What Is a Honeypot?

A honeypot is intentionally placed as a trap.

The channel appears accessible enough for automated spam accounts to discover or interact with, but legitimate members should be clearly instructed not to use it.

If someone triggers the honeypot, Bleed applies the punishment configured for that channel.

This can provide another layer of protection against:

• automated spam accounts
• raid bots
• mass-advertising accounts
• malicious scripted behavior
• accounts blindly posting into every available channel

➕ Create a Honeypot

,honeypot add [channel] [punishment]

Adds a channel to Bleed’s honeypot system and assigns the punishment that should occur when it is triggered.

Permission Required: Administrator

⚠️ Choose the punishment carefully.

A false trigger could affect a legitimate member, so the channel should be designed so ordinary users have no reasonable reason to interact with it.

📋 View Honeypots

,honeypot list

Displays all channels currently configured as honeypots.

Permission Required: Administrator

Use this periodically to confirm that your active honeypots are still intentional and properly placed.

➖ Remove a Honeypot

,honeypot remove [channel]

Removes a channel from Bleed’s honeypot system.

Permission Required: Administrator

This stops the channel from functioning as an automatic trap.

⚖️ Laws of Honeypot Use

I. Never Trick Legitimate Members

A honeypot should catch automated or obviously malicious behavior—not curious members.

II. Keep It Away From Normal Navigation

Do not place honeypot channels where members could reasonably mistake them for ordinary discussion spaces.

III. Use Proportionate Punishment

Configure only the level of punishment justified by triggering the trap.

IV. Review Before Escalating Further

If a honeypot action creates a moderation case, review available logs before applying additional punishment.

V. Do Not Publicize Its Mechanics

Members may know that automated security exists, but avoid publishing unnecessary details that would make the trap easier to evade.

VI. Test Carefully

Verify channel permissions and Bleed behavior before relying on the system during an actual raid.

📜 Quick Reference

,honeypot add [channel] [punishment] — Create a honeypot

,honeypot list — View configured honeypots

,honeypot remove [channel] — Remove a honeypot

🍯 A honeypot should catch those attacking the Archive—not those merely wandering through it.