Incident CheckRead-only · no wallet needed

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.

Your profile address, not your extension or controller key. A profile link that contains the address also works.

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.

When you are done, check again here. The result shows the exact value read from the chain.

Good to know

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.

The eleven addresses