Fact-check findings
What an automated fact-checker found when it re-read LCX against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #7[unverifiable][awaiting moderator]in the timeline
“Liechtenstein implements MiCAR; LCX reportedly files a formal MiCA license application.”
reviewerLiechtenstein implements MiCAR in Feb 2025; LCX reportedly files a formal MiCA application (no source given).Entry has no source or URL. An application exists, but the February 2025 date was not found.
stale
2 claimsThe claim was accurate when written but events since have overtaken it.
- #5[stale][awaiting moderator]in section: Regulatory Status and Licensing
“LCX operates under MiCAR transition arrangements and has stated a target compliance date of December 31, 2025.”
reviewerLCX operates under MiCAR transition arrangements with a target compliance date of December 31, 2025.The December 2025 target date has passed (today is 2026-11-01) and LCX's own site says it is unauthorised and winding down EEA service. The page's wording implies ongoing compliant operation.Proposed correction (not yet applied)LCX has applied to the FMA for MiCA crypto-asset service provider authorisation and the application remains under review; LCX states it is not currently authorised under MiCA, does not offer crypto-asset services to persons in the EEA while the application is pending, and limits existing EEA clients to withdrawals during a wind-down. - #6[stale][awaiting moderator]in section: Current Operations and Developments (2024–2026)
“As of 2025–2026, LCX continues to operate as a regulated crypto exchange in Liechtenstein.”
reviewerLCX continues to operate as a regulated exchange in Liechtenstein.The cited Gate blog is promotional and predates the EEA wind-down notice.Proposed correction (not yet applied)As of 2025–2026, LCX continues to operate from Liechtenstein under its TVTG registrations but, per its own site, is not yet authorised under MiCA and has wound down service to EEA clients pending that authorisation.
link rot
1 claimA cited source no longer resolves or no longer says what the page attributes to it.
- #8[link rot][awaiting moderator]in section: User Complaints and Platform Conduct
“https://www.cybercriminal.com/132701/lcx-com-trust-issues-and-high-risk”
reviewerTrustpilot/Scamadviser/complaint source: cybercriminal.com article cited for user complaints.The domain is parked; the page's own archive snapshot is a for-sale page, so the source no longer supports anything.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in section: January 2022 Hot Wallet Hack
“The converted ETH was deposited into Tornado Cash using the 100, 10 and 1 ETH contracts by approximately 11:12 PM GMT.”
reviewerThe converted ETH was deposited into Tornado Cash (cited to the incident report among others).Tornado Cash laundering is corroborated by secondary reporting, but not by the official report. The specific 11:12 PM GMT timing was not checked against the TRM page. - #4[partially supported][awaiting moderator]in the timeline
“https://www.lcx.com/lcx-hack-update/”
reviewerMonerium froze ~611,000 EURe; cited to the LCX Hack Update page.The fact is real but the cited URL is the wrong page. The event text also contains reviewer-facing wording ('The survivor page also dates... the other page') that does not belong in a published timeline. - #9[partially supported][awaiting moderator]in section: Security Posture and Post-Incident Response
“The exchange resumed deposits and withdrawals on January 28, 2022, about 20 days after the incident.”
reviewerExchange resumed deposits and withdrawals on January 28, 2022, about 20 days after the incident.Full resumption on Jan 28 is right; services were restored in stages from Jan 12.
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: January 2022 Hot Wallet Hack
“On January 8, 2022, between 11:23 PM and 11:37 PM CET, an unauthorized actor gained access to LCX's Ethereum hot wallet(s) and drained multiple token balances in a coordinated sweep.”
reviewerAbout $7.94 million was stolen on January 8, 2022 between 11:23 PM and 11:37 PM CET, with the listed token breakdown.Amounts and window match the official incident report. - #3[confirmed][no action needed]in section: Fund Recovery and Legal Actions
“By LCX's own account, approximately 60% of the stolen funds had been frozen as of June 2022.”
reviewerLCX froze about 60% of stolen funds, including 500 ETH at Coinbase Europe and 1,274,249 USDC; the NY complaint was filed June 1, 2022.Confirmed against the official update. - #10[confirmed][no action needed]in section: Regulatory Status and Licensing
“In December 2024 LCX filed a pre-application for a pan-European Markets in Crypto-Assets Regulation (MiCA) license with the FMA;”
reviewerLCX filed a MiCA pre-application in December 2024.Corroborated by the press release and search results.