Community Management
Communities are often the foundation of Web3 projects, serving as the primary connection point between organizations and their users. However, they also represent one of the largest attack surfaces. From community members and moderators to founders and executives, every individual within an ecosystem can become a target of social engineering, phishing, impersonation, account compromise, malware, and other attacks across platforms such as Discord, Telegram, X (formerly Twitter), Google Workspace, and beyond.
When a community channel is compromised—whether through a malicious link, a compromised team member account, fraudulent support interaction, or a coordinated social engineering campaign—it can quickly become a launch point for wider attacks that impact users, project assets, and organizational reputation.
This framework provides essential guidance, best practices, and security controls to help organizations build, operate, and maintain secure communities. The following sections explore platform-specific recommendations and defensive strategies in greater detail, enabling teams to reduce risk while fostering safe and trusted environments for their communities.
Platform frameworks
| Platform | What it covers | Link |
|---|---|---|
| Discord | Server permissions, role hygiene, raid protection, bot vetting, and anti-impersonation | → Discord framework |
| X (Twitter) | Account security, impersonation risks, API token scope, and official channel hygiene | → X framework |
| Telegram | Two-step verification, phone number privacy, admin permissions, and man-in-the-group attacks | → Telegram framework |
Security domain index
| Domain | What it covers | Framework |
|---|---|---|
| Authentication & passwords | Unique credentials per service, hardware token preference, and 2FA requirements for linked email accounts | Operational Security → |
| Phishing & social engineering | Official channel verification, DM policies, and recognizing impersonation tactics targeting your team and users | Security Awareness → |
| Operational security | Device hygiene, software update discipline, and reducing the attack surface used to manage community channels | Operational Security → |
| Emergency response | Pre-defined protocols for account compromise, rapid revocation of access, and community notification procedures | Incident Response → |