Manage your whitelist keys, HWID resets and hub access
Configuration
Kill switch — global pause
When paused, new executions are blocked (users are kicked with your message). Already-running users are not disturbed — they're only blocked when they re-launch. Use this to lock everything down while you patch a vulnerability, then Resume.
Total keys
—
Active keys
—
Disabled keys
—
Expired keys
—
Flagged keys
—
Dashboard
Active users (24h)
—
Total auth requests
—
Auth sessions (sum)
—
Key actions
Create new key
Key details (also auto-added to KV):
Tracked keys
Load from server pulls every key straight from KV (the source of truth). Generated keys are also auto-tracked locally, and you can manually add an existing key below.
HWID / device-ID blacklist
Blocks a HWID (or device-ID) across all keys, before any key check — costs nothing per auth (folded into the pause config).
Unauthorized attempts
HWIDs that ran your loader (valid signature) but had an invalid / disabled / expired key — i.e. people using the script un-whitelisted. One click to blacklist. (Logged at most once per 10 min per HWID; auto-expires after 7 days.)
Tamper / hook kicks
HWIDs the loader kicked for hooking / tampering (it reports the reason just before killing the session — best-effort, a fully-hooked client may block it). One click to blacklist.