# Blocked Nicknames

{% hint style="info" %}
**Premium Feature** — Nickname blocking requires a Premium subscription. [Compare plans →](/securitybot-knowledge-hub/plans-and-pricing/plans-and-pricing.md)
{% endhint %}

SecurityBot allows you to block specific nicknames that are commonly used by scammers, such as “Giveaway Bot,” “Support Team,” or other misleading terms. This helps prevent users from impersonating staff or official bots within your community.

***

### How to Block Nicknames

To block a specific nickname:

```
/user_filters nickname block name: [nickname]
```

Example:

```
/user_filters nickname block name: Support Team
```

To unblock a nickname:

```
/user_filters nickname unblock name: [nickname]
```

To view all currently blocked nicknames:

```
/user_filters nickname view
```

{% hint style="warning" %}
Blocked names are **NOT** applied retroactively! If a user is already using a name when you block it, they will not be kicked. This ensures you dont remove a real user whos name you are trying to protect!
{% endhint %}

***

### Suspicious Name Detection

In addition to exact matches, SecurityBot also monitors for **suspiciously similar nicknames,** even if special characters or lookalike letters are used to evade filters.

These names won’t be auto-blocked, but a warning will be sent to your log channel so you can take action manually.

{% hint style="warning" %}
**Note:** Users with suspicious names will not be removed automatically. Review SecurityBot logs regularly to monitor impersonation attempts.
{% endhint %}

***

### Pattern Blocking

You can block names that **start with**, **end with**, or **contain** specific words using pattern syntax. This helps prevent variations like “SecurityBot Support” or “JPG Store Support Team” from slipping through.

Use the `+` symbol to indicate “any number of characters” before or after your pattern.

|                         | Command                                             | Example Blocked Names                                                                                       |
| ----------------------- | --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Name starts with string | `/user_filters nickname block name: SecurityBot+`   | <p><code>SecurityBot</code></p><p><code>SECURITYBOT SUPPORT</code></p><p><code>securitybot staff</code></p> |
| Name ends with string   | `/user_filters nickname block name: +notifications` | `Claymates notifications` `SPACEBUDZ NOTIFICATIONS`                                                         |
| Name contains string    | `/user_filters nickname block name: +support+`      | <p><code>support bot</code></p><p><code>open-support-ticket</code></p><p><code>JPG Store Support</code></p> |

***

### Best Practices

* Block common scam terms like “giveaway”, “support”, “team”, “mod”, "airdrop"
* Use pattern blocking for flexible coverage
* Monitor logs for suspicious name alerts
* Review and adjust your blocked list periodically using `/user_filters nickname view`

{% hint style="info" %}
Only users with the admin role or Administrator permissions can manage blocked nicknames.
{% endhint %}

***

Next up: Learn how to detect and respond to impersonators using copied profile pictures with [Avatar Protection](/securitybot-knowledge-hub/bot-guide/anti-impersonation-tools/avatar-protection.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://securitybot.gitbook.io/securitybot-knowledge-hub/bot-guide/anti-impersonation-tools/blocked-nicknames.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.