Fact-check findings
What an automated fact-checker found when it re-read MultiversX (EGLD) 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.
disputed
1 claimThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #11[disputed][awaiting moderator]in section: Historical Context: 2022 Bridge Exploit
“Historical Context: 2022 Bridge Exploit”
reviewerSection heading describes the 2022 incident as a bridge exploitThe page's own body describes a Maiar DEX smart contract exploit, which contradicts the 'Bridge' heading. I did not fetch the 2022 report, so the correction relies on the page's body text and my own knowledge of the 2022 event.Proposed correction (not yet applied)Historical Context: 2022 Maiar DEX Exploit
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #6[unverifiable][awaiting moderator]in section: Attacker Response and Containment
“The User Protection Fund was referenced in reporting by ETHNews as part of MultiversX's safeguarding infrastructure in connection with this incident, though specific deployment details were not confirmed in available sources.”
reviewerThe User Protection Fund was referenced by ETHNews in connection with this incidentThe cited ETHNews article does not mention the fund, so the attribution could not be supported. Consider removing the sentence. - #10[unverifiable][awaiting moderator]in section: Technical Vulnerability
“According to reporting by CryptoTicker and community analysis, the specific vulnerability allowed a malicious contract to call 'executeOnDestContextByCaller' inside an asynchronous callback.”
reviewerThe cryptoticker article is cited for Bithumb/Coinbase/Kraken and technical detailsThe function name is not in the cited CryptoTicker piece. The egld-esdt-swap target was not checked against the other cited sources.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #7[partially supported][awaiting moderator]in section: Attacker Response and Containment
“no law enforcement action had been publicly announced as of the investigation date”
reviewerNo law enforcement action publicly announcedTechnically accurate but omits that law-enforcement involvement was claimed by the team. - #8[partially supported][awaiting moderator]in section: Attacker Response and Containment
“MultiversX stated that the attacker's accounts were identified and frozen through coordination with major cryptocurrency exchanges, which were provided a blacklist of associated wallet addresses.”
reviewerAttacker accounts were identified and frozen via exchange coordinationThe page correctly attributes this to MultiversX. The summary states it as fact ('the attacker's wallets were identified and frozen'), and the blacklist detail was not located in the source. - #9[partially supported][awaiting moderator]in the timeline
“MultiversX confirms via @MultiversX on X that a VM-level atomicity exploit caused invalid state changes; engineering is preparing a fix for shadow-fork validation.”
reviewerMultiversX confirmed the exploit via X on Sept 21 (timeline)ETHNews places the confirmation on Sept 19-20. The X post could not be fetched to give its date. The timeline's Sept 19 entry already includes the exploit, so the Sept 21 date for confirmation is questionable.
confirmed
7 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Exchange Restrictions and Market Impact
“suspended EGLD/KRW, EGLD/BTC, and EGLD/USDT deposits and withdrawals at 5:47 p.m. KST on September 19 and applied a formal trading caution designation on September 21”
reviewerUpbit suspended deposits/withdrawals at 5:47 p.m. KST on Sept 19 and designated caution markets on Sept 21Matches crypto.news. - #2[confirmed][no action needed]in section: Exchange Restrictions and Market Impact
“EGLD price declined approximately 8.7%, from roughly $4.14 on September 18 to approximately $3.78 on September 20, while trading volume surged from $3.35 million to $10.18 million over the same period.”
reviewerEGLD fell about 8.7% from $4.14 (Sept 18) to $3.78 (Sept 20), volume $3.35M to $10.18MFigures match. Note the price later recovered (CryptoTicker reports about $4.53 in early October), which the summary's 'declined during the halt' framing does not mention. - #3[confirmed][no action needed]in the timeline
“Kraken first flagged possible EGLD funding-gateway delays at 9:58 a.m. ET, before the public exploit disclosure.”
reviewerKraken first flagged EGLD delays at 9:58 a.m. ET on Sept 16Confirmed by TokenPost. - #4[confirmed][no action needed]in section: Exchange Restrictions and Market Impact
“Kraken placed EGLD in cancel-only mode at 21:00 UTC on September 19”
reviewerKraken placed EGLD in cancel-only mode at 21:00 UTC Sept 19Confirmed by TokenPost; CryptoSlate agrees on Sept 19. - #5[confirmed][no action needed]in section: Incident Overview
“Block production resumed on September 24, 2026, following deployment of a recovery upgrade, representing a halt of approximately five calendar days.”
reviewerHalt and restart: Sept 19 to Sept 24, about five daysSupported by CryptoSlate and TokenPost. - #12[confirmed][no action needed]in the timeline
“Outcome pending as of investigation date.”
reviewerUpbit review scheduled for Oct 19-23; outcome pendingAccurate as of Oct 4. The window has since closed and I found no reported outcome. - #13[confirmed][no action needed]in the timeline
“Kraken closes its EGLD incident; EGLD/EUR trading resumes on Kraken.”
reviewerKraken closed incident Oct 1 and resumed EGLD/EURConfirmed.