LUKSO incident · 17–18 Nov 2026
Check your
Universal Profile
Paste your Universal Profile address. This page reads your profile on-chain and tells you whether the attacker key or any of the ten recovery profiles used in the attack still has permissions on it, and what to do about it.
How to remove a controller correctly
The permission value for the address must end up empty (0x). Lowering permissions is not enough.
Common mistake: unticking permissions in a UI leaves the value at 0x1500. That is SUPER_TRANSFERVALUE + SUPER_CALL + SUPER_STATICCALL, which still lets the address move LYX and tokens. Several profiles were left like this.
- Use remove controller rather than editing individual permissions, or
- make sure every permission is off, including the three “super” ones, or
- call
setDataon your profile with the data key shown in your result and value0x.
When you are done, check again here. The result shows the exact value read from the chain.
Good to know
- Removing the recovery controller turns off LUKSO’s 2FA recovery for that profile. Make sure you have another backup first, for example the private key of your extension controller. During this incident, removing it is still the safe choice.
- Importing a profile or adding a new device can register the recovery controller again. Check again afterwards.
- If an affected profile is itself a controller on other profiles or contracts, those are at risk too.
- Removing controllers does not recover funds that were already taken.
- Don’t rely on the controller list in a wallet or app. A recovery controller has been seen missing from the list while its permission was still set. This page reads the permission itself, which is what your profile’s Key Manager enforces.
What this page checks
For each of the eleven incident addresses below, it reads the data key AddressPermissions:Permissions:<address> on your profile, directly from rpc.mainnet.lukso.network, at one block. Empty or all zeros means no permissions; any other value means action is needed.
It covers only these eleven addresses. It is not a general safety check, and a further recovery profile that was not used in the attack has not been ruled out. LUKSO’s official channels are the authority on next steps; if their instructions differ from this page, follow theirs.