← Back to Blog Moderation

How to Prevent and Respond to Brigading

By the InteractInk Team·4 min read·2026-10-22
How to Prevent and Respond to Brigading — InteractInk guide cover

Brigading happens when a group from outside, often organised on another site or chat, descends on your community to flood it with hostile comments, mass votes or reports. It might be aimed at a single member, a controversial post or the whole space. Because it is coordinated, it can overwhelm moderators in minutes and leave members shaken. You cannot always stop someone from calling for an attack, but you can make your community a hard target and recover quickly. This guide explains how.

Recognise the pattern

Brigades have recognisable features. A sudden spike of traffic to one thread, many new or inactive accounts posting similar messages, matching phrases and timing, strange voting patterns and a link or reference to your community on another platform. Real controversy involves varied voices over time, while a brigade is fast, repetitive and from accounts with little history. Learning the signs lets you act early.

Prepare before it happens

Preparation does most of the work. Decide who has authority to switch on emergency measures, write a short checklist and make sure several moderators know how to use the tools. Know your platform's controls: who can post, who can vote and how reports work. Many of the steps align with how to moderate during a crisis or raid, so build the two plans together.

A sudden surge of coordinated comments — InteractInk community guide illustration
A sudden surge of coordinated comments

Add friction for new accounts

Brigaders usually arrive with fresh or throwaway accounts. Gentle restrictions blunt them: limit posting by new accounts, hold first posts for review, require a short waiting period before voting or linking and use verification at signup. These measures cost real newcomers very little but make a brigade much harder. The same tools appear in how to prevent bots and fake accounts in your community.

Protect the target

If a person or a post is the target, support them. Offer to hide or lock the thread, limit who can reply and give the member control over comments. Reach out privately, listen and explain what you are doing. Check that personal information is not being shared, and follow how to handle doxxing and privacy leaks if it is. A member who feels defended stays loyal.

Defences from prevention to recovery — InteractInk community guide illustration
Defences from prevention to recovery

Contain the surge

When a brigade hits, act in the order of harm. Lock or slow the affected threads, switch on posting limits and remove the worst content. Pause new signups if needed. Do not argue with participants, because attention is what they want. Keep the response calm and procedural. Contain first, investigate later.

Handle the reporting system with care

Brigades often abuse report buttons to get legitimate members penalised. Do not act on volume alone: review reports individually and check whether they come from fresh or linked accounts. Treat a burst of near-identical reports against one person as a warning sign rather than evidence. The balanced approach in how to handle user reports fairly keeps you from punishing the wrong people.

Distinguish brigades from real disagreement

Not every surge is an attack. A post may spread to a sympathetic audience, and many genuine people may respond with real opinions. Respond differently: set ground rules for the thread, invite respectful discussion and remove only rule-breaking content. Keep behaviour standards the same for everyone. Guidance on keeping neutrality is in how to moderate controversial topics without taking sides.

Communicate with your members

Tell members briefly what is happening, what you are doing and what they can do. Ask them not to engage with attackers and to report instead. Avoid naming outside groups in detail, and do not inflame the situation. Honest updates keep fear from turning into rumour. When it ends, say so, and thank the community for its patience.

Work with other platforms

If the brigade was organised elsewhere, you can sometimes report it to that platform, especially when it involves harassment or personal information. Keep clear evidence: screenshots, timestamps and links. Do not rely on the outcome, but a report can help and creates a record. Evidence habits from how to keep a moderation log that protects you matter here too.

Recover and learn

After the surge, clean up and loosen emergency settings gradually. Hold a debrief with your team: which signals came first, which tools helped and what was missing? Update your plan. Check on affected members and moderators, since a brigade can be draining; see moderator burnout: warning signs and how to fix it. Each incident, handled well, strengthens your defences.

The bottom line

Preventing brigading means knowing the pattern, preparing a plan, adding friction for new accounts and protecting targets. When it strikes, contain the surge, handle reports carefully, communicate calmly and avoid feeding the attackers. Afterwards, recover in stages and learn from the event. A community that is ready can weather a brigade and come out with trust intact.

Frequently asked questions

How is a brigade different from a viral post?

Brigades are coordinated, fast and made up of new or low-history accounts, while viral attention brings varied, genuine voices over time.

Should I lock the thread being brigaded?

Often yes, at least temporarily. Locking or limiting replies gives you time to assess and protects the target.

Can I ban everyone who joined in?

Act on rule-breaking behaviour and clearly linked accounts, but review genuine members individually.

How do I protect myself from false reports?

Review reports individually and treat bursts of similar reports against one person with suspicion.

Moderation

Comments

Loading comments…