Blacklist

The Blacklist section is used to strengthen the security of your application. Here you can block a specific IP or HWID to prevent that user or device from accessing your application.

Simple meaning:

IP Blacklist → Block a specific internet IP address
HWID Blacklist → Block a specific device (hardware ID)

Where Can This Be Used?

1) Prevent Abuse / Spam

If a user is spamming chat, abusing the API, attempting brute-force attacks, or sending suspicious requests,
you can blacklist their IP or HWID so they cannot access the application or API again.

2) Block Cracked / Leaked Loaders

Sometimes a loader gets leaked and starts running on multiple PCs.
If you identify a device using a cracked version:

Add its HWID to the blacklist
Login, initialization, and license requests from that device will be blocked

3) Block VPN / Proxy Users

Some users attempt to bypass restrictions using VPNs or proxies.
If certain IP ranges appear suspicious (for example datacenter IPs), you can:

Blacklist those IP addresses to block access

4) Chargebacks / Fraud / Non-paying Users

If a user causes payment issues, performs a chargeback, or commits fraud,
you can permanently block access to your application by blacklisting their device HWID or IP address.

5) Panel-Level Protection (Admin Control)

Staff or managers often need to take immediate action:

Add a blacklist entry with one click to disable access
Remove the entry later to restore access

What Happens When You Use It?

1) API Requests Are Blocked

When a client sends an init, login, or license request from a blocked IP or HWID, the backend will check the blacklist and:

The request will be rejected
The user will no longer be able to log in or use the application

2) Device-Level Ban (HWID)

When an HWID is blacklisted:

The application stops working on that specific PC/device
Even if the user creates a new account, the same device will remain blocked

3) Network-Level Ban (IP)

When an IP address is blacklisted:

Access from that IP address is blocked
If the user changes their IP (VPN, reboot, ISP change), they may bypass the block

Therefore, generally:

IP blocking is best for quick temporary actions
HWID blocking is best for permanent bans

Important Notes (Practical)

HWID bans are the strongest because they are device-based
IP bans are useful for quick actions but can change with dynamic IPs
If your system checks the blacklist during init/login, the effect will be immediate
Whitelist logic is different — the blacklist is purely a block list

Example Use Cases

Chat spammer: Block their IP
Cracked loader user: Block their HWID
Repeated incorrect passwords: Temporarily block the IP (abuse prevention)
Fraudulent buyer: Block both HWID and IP

Overall, the Blacklist feature gives you direct control to protect your AuthVaultix applications from abuse, cracks, fraud, and spam.

Blacklist

Blacklist#

Where Can This Be Used?#

1) Prevent Abuse / Spam#

2) Block Cracked / Leaked Loaders#

3) Block VPN / Proxy Users#

4) Chargebacks / Fraud / Non-paying Users#

5) Panel-Level Protection (Admin Control)#

What Happens When You Use It?#

1) API Requests Are Blocked#

2) Device-Level Ban (HWID)#

3) Network-Level Ban (IP)#

Important Notes (Practical)#

Example Use Cases#

Blacklist

Where Can This Be Used?

1) Prevent Abuse / Spam

2) Block Cracked / Leaked Loaders

3) Block VPN / Proxy Users

4) Chargebacks / Fraud / Non-paying Users

5) Panel-Level Protection (Admin Control)

What Happens When You Use It?

1) API Requests Are Blocked

2) Device-Level Ban (HWID)

3) Network-Level Ban (IP)

Important Notes (Practical)

Example Use Cases