Detecting Fake Invites: A Discord Mod's Playbook (2026)

PeakBot is an AI-powered Discord bot with dedicated fake-invite detection on the free tier — most invite trackers don't have this. Fake invites inflate leaderboards, hide raid waves, and let users farm rewards by inviting alt accounts. This playbook covers the patterns, the detection rules, the manual review workflow, and exactly how to set up PeakBot to catch fakes the moment they happen.

Key Takeaways

• Fake invites are accounts joining via your invite link with no intent to participate — alts, bots, paid join farms, and reward-farming throwaways.
• The five reliable detection signals are: account age, no avatar, instant leave, join clusters, and invite-to-message ratio.
• PeakBot's free invite tracker flags fake invites automatically and excludes them from leaderboards — a feature MEE6, Dyno, and most invite-only bots paywall or simply don't have.
• Manual review is still required for borderline cases. Build a 3-step audit workflow: pull the invite log, sort by leave-rate per inviter, spot-check the top offenders.
• Reward-farming is the single biggest reason servers care: if you run an invite giveaway without fake-invite detection, you will pay a prize to someone who botted alts.

What Are Fake Discord Invites, Exactly?

A "fake invite" in Discord is any join attributed to a user's invite link that doesn't represent a real, engaged member. The Discord API itself doesn't have a "fake" flag — every join through an invite increments that invite's counter. So whether something is "fake" is a judgment call your bot or your mods make using behavioral signals after the join.

Three flavors show up most often:

• Alt-account fakes — A member creates throwaway accounts on Discord, joins your server through their own invite link, and pads their invite count to win a reward.
• Botnet fakes — Paid services (yes, those exist; they're advertised on shady Discord servers and on Telegram) that drop hundreds of fresh accounts through a target invite link in 60 seconds, often as part of a raid or join-to-leave griefing run.
• Drive-by fakes — Real humans who joined, never said a word, and left within minutes. Counted as an invite but added zero value.

The Discord developer docs (Discord Invite object reference) confirm there's no native "is this account real" property — uses increments on every join. That's the gap fake-invite detection fills.

Why Fake Invites Actually Hurt Your Server

It sounds like a small problem until you've run an invite giveaway. Here's where the damage accumulates:

1. Inflated metrics. If your member counter shows 5,000 but 1,200 of those joined and left silently within 24 hours, your engagement rate is roughly a quarter of what your dashboard implies. You'll plan content for a server you don't actually have.

2. Hidden raid waves. A common raid pattern: 200 alt accounts join through one invite link over 90 seconds, post a phishing message, and leave. If your invite tracker doesn't flag the cluster, you only see "200 new members" — not "200 fakes from one invite." Anti-raid tooling catches the spam, but the attribution is what tells you which invite to nuke. We cover the broader response in our Discord raid protection guide.

3. Reward farming. If you run an "invite 10 friends, get a custom role" promotion and don't filter fakes, the leaderboard fills with people inviting their own alts. Real inviters lose. They notice. They leave.

4. Reputation damage. Inflated counts read as fake servers to potential members. Discord users have gotten very good at spotting a server with 8,000 members and a quiet #general — they assume bot-padded and bounce.

5. Discord ToS exposure. Discord's policy on platform manipulation (Community Guidelines) treats coordinated alt-account activity as a violation. Letting it run on your server is a risk to your server, not just to the offender.

The Five Detection Patterns That Actually Work

After running fake-invite detection on a network of 500+ servers, these are the signals that earn their keep.

1. Account age under 7 days. Cheapest and most effective filter. The ratio of fakes-to-reals in the under-7-days bucket is roughly 8:1 in our data. Discord exposes creation timestamps via the Snowflake ID.

2. No avatar, no banner, default username. A real user usually customizes something in their first hour. An account with the default avatar, no display name, and a username like user.78492 is almost always a throwaway.

3. Joined and left within 5 minutes. If a session lasted shorter than the time it takes to read your rules channel, they were never going to engage. PeakBot logs join and leave timestamps per inviter.

4. Join clusters by inviter. Five accounts joining through one invite link within 30 seconds is suspicious. Twenty in 60 seconds is a botnet. The most useful raid signal.

5. Invite-to-message ratio. Long-tail: an inviter whose 50 invites collectively posted 3 messages is farming. Real, popular members' invites lurk and chat at normal rates.

"We caught a guy padding his invite count with 47 fresh accounts before our giveaway closed. PeakBot's leaderboard already had him filtered out — fake count 47, real count 0. Without it we'd have shipped him a $50 gift card." — server admin, 12,000-member gaming community

How Does PeakBot's Fake-Invite Detection Compare to Other Bots?

Most invite trackers count joins and stop there. The few that detect fakes either gate it behind a Premium tier or run a single rule (usually account age). PeakBot ships all five signals on the free plan.

Bot	Tracks invites	Detects fakes	Free?	Notes
PeakBot	Yes	Yes — 5 signals (age, customization, instant-leave, clusters, msg ratio)	Free	Auto-excludes fakes from leaderboards. Configurable thresholds.
MEE6	Yes	Limited (account age only)	Premium ($11.95/mo)	Fake-invite filter is a Premium feature (MEE6 Premium).
InviteTracker	Yes	Yes — partial (age + leaves)	Free w/ Premium upsell	Decent free tier; cluster detection requires Premium.
Dyno	Yes (basic)	No	Free	Counts invites; no fake detection logic. (Dyno Premium)
Carl-bot	No native invite tracker	N/A	—	Strong moderation, but invite tracking isn't a core feature.
InviteManagement	Yes	Yes (age + leaves)	Free + Premium	Solid niche bot, but single-purpose — no mod, no XP, no welcome.
Ticket Tool / Arcane / others	No	No	—	Single-feature bots; not relevant here.

The gap is real. According to invite-tracker comparisons on top.gg and discussion in r/discordapp, the most-asked feature in invite-tracking threads is fake-invite filtering — and the most common answer is "you'll need Premium for that." PeakBot ships it free as part of the features list.

How Do I Set Up Fake-Invite Detection in PeakBot?

Setup takes about three minutes:

1. Open the dashboard. Go to your server's /invite-tracker page in PeakBot.
2. Enable Fake Invite Detection. Toggle on at the top — this turns on the five-signal scoring engine.
3. Tune thresholds. Defaults: 7-day account age, 300-second instant-leave, 5 joins in 60 seconds for clusters. Lower for stricter servers.
4. Set leaderboard behavior. Choose "Exclude fakes from leaderboard" (recommended) or "Show fakes with strikethrough."
5. Wire the alert channel. Pick a mod-only channel where PeakBot posts cluster and high-fake-rate alerts. The single most valuable setting.
6. Set the auto-action. Optional. Auto-kick above a confidence threshold, or flag for manual review. Start with "flag only" for two weeks, then turn on auto-kick.

Detection runs on every join — no scheduled job to babysit. If you're also running anti-nuke (you should be — see our Discord anti-nuke protection guide), the two work together: anti-nuke handles destructive actions, fake-invite detection handles the entry vector.

The Manual Review Workflow That Actually Catches Things

Bots catch the obvious cases. The interesting fakes — the ones where someone is methodical about avatars and account aging — slip past automated rules. That's where a weekly manual audit pays off.

Step 1: Pull the invite leaderboard. PeakBot exposes this on the dashboard or via the /invites top command. Sort by total invites for the rolling 30-day window.

Step 2: Compute leave-rate per inviter. For each top-10 inviter, look at the percentage of their invites who are still in the server. A healthy ratio is 40–70%. An inviter at 95% kept-rate is great. An inviter at 8% is farming or got hit by a botnet through their link (either way, investigate).

Step 3: Spot-check the suspect. Click into the inviter's invite log. Look at the timestamps. Twenty joins in five minutes from accounts created the same week? You have your answer.

Step 4: Decide. Three responses, ranked by severity:

• False positive — actual community member with one bad cluster. Whitelist them and move on.
• Casual rule-breaker — DM them, warn that fake invites get them disqualified from giveaways, watch for repeat behavior.
• Bad actor — kick or ban, revoke their invite link, and check whether the joining accounts are tied to a broader raid pattern.

This 15-minute weekly ritual is what we ran across the network — fake-invite-related issues dropped roughly 80% within a month. The full moderation framework lives in our complete Discord moderation guide.

What Real Discord Mods Are Saying

The pattern recognition isn't theoretical. A representative thread on r/discordapp ("Best way to catch fake invites for giveaways?") had 200+ upvotes and the top answer pointed to bot-side detection plus a manual leaderboard audit before paying out — basically the workflow above.

A Trustpilot review of MEE6 (trustpilot.com/review/mee6.xyz) flagged the paywall on fake-invite filtering specifically: "Had to upgrade just to stop people inviting alts. Annoying for a feature that should be standard." PeakBot was built on that exact gripe — fake-invite detection should be standard, not Premium.

The other recurring case study from server-mod Discord communities is the "phantom giveaway winner": someone wins, gets DMed for delivery info, ghosts. Almost always it's an alt account, and almost always the inviter behind them was farming. With fake-invite detection turned on before the giveaway, the inviter never reaches the leaderboard.

When Fake-Invite Detection Is Not Enough

Detection is a layer, not a wall. Three scenarios where you need additional protection:

Sustained botnet raid. If 500 fakes join in 90 seconds, fake-invite detection flags them — but anti-raid is what stops the spam wave. Run them together. PeakBot's anti-raid bundle is also free; setup is in our raid protection guide.

Compromised mod account. Fake invites are about the entry layer; nukes happen after a malicious account gets elevated. That's why you also need anti-nuke — it caps how much damage any single user (or compromised mod) can do. Walkthrough in our anti-nuke setup guide.

Real human farming. If someone's gaming the system with their own family members and roommates' real accounts, no automated rule will catch it. That's a community-management problem, not a bot problem.

The point: detection plus active moderation plus layered security. No single tool replaces the others. PeakBot bundles all three on the free tier; MEE6, Dyno, and Wick split them across plans.

Frequently Asked Questions

What counts as a fake Discord invite?

Any account that joins through your invite link without contributing — alt accounts, bot-farm joins, and members who leave within minutes of joining. Discord doesn't natively label invites as fake; bots like PeakBot apply behavioral rules (account age, instant leave, customization, cluster timing) after the join. The "fake" label is always probabilistic, which is why PeakBot exposes confidence scores per detection.

Will PeakBot's fake-invite detection give me false positives?

Occasionally, yes — typically with brand-new Discord users who join from a shared link during a livestream or community event. PeakBot's defaults are tuned to under 5% false-positive rate in our internal testing. If you're seeing more than that, raise the account-age threshold from 7 days to 3 days and turn off cluster detection during scheduled events. Both options live on the dashboard.

Does Discord penalize servers for having fake members?

Not directly — but Discord's Community Guidelines prohibit coordinated platform manipulation, which includes alt-account farming. Servers that get reported for botted membership counts can lose Partner or Verified status, and in egregious cases lose the server entirely. Fake-invite detection helps you stay on the right side of that policy by giving you visibility into who's farming.

Is fake-invite detection free in PeakBot?

Yes. The full detection stack — five signals, configurable thresholds, leaderboard filtering, mod alerts, and the manual review tools — is on PeakBot's free tier with no time limit. Pro ($8.50/mo, currently $4.25/mo with code PEAK50) unlocks the AI Server Builder and advanced AI features, but the entire invite-tracking and security suite stays free. Details on the pricing page.

What if a real user just happens to be new?

The seven-day age cutoff is a heuristic, not a verdict. PeakBot doesn't auto-kick on age alone — it weights age alongside customization, session length, and cluster behavior. A real new user with an avatar who joins, says hi, and stays will not be flagged. The system is designed to catch the combination of signals, not any single one in isolation.

How do I migrate from MEE6 invite tracking to PeakBot?

Install PeakBot via the homepage, then on the dashboard's invite-tracker page enable "Import from MEE6." PeakBot pulls historical invite counts via the Discord audit log (back to whatever Discord retains, typically 90 days) and starts fake-invite scoring from the moment you enable it. Going forward you can leave MEE6 enabled in parallel for a week to compare leaderboards before fully cutting over. Walkthrough on our docs.

Can I run fake-invite detection alongside another bot?

Yes. PeakBot's invite tracker is read-only on the Discord side — it observes joins via gateway events and doesn't conflict with other invite trackers. The most common combo we see is PeakBot for detection plus a single-purpose giveaway bot. That said, if you're already running PeakBot you don't need a separate giveaway bot — giveaways are bundled into the free feature set.

Conclusion

Fake-invite detection is one of those features that looks niche until the day you run a giveaway, an event, or a partnered launch — and suddenly your leaderboard is 60% throwaway accounts. The mods who treat it as standard infrastructure save themselves the embarrassment.

PeakBot bundles the detection engine, the manual review workflow, and the broader security stack (anti-nuke, anti-raid, automod) into a free tier that competes with MEE6 Premium and Dyno Premium combined. If you're running a server larger than 100 members, turn it on before your next giveaway. Visit peakbot.pro to install, or browse the full blog for more mod playbooks.