← Nexerareviewed 2026-11-01 · 14 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Nexera against the sources the page cites. Only the most recent review is shown.
Read this first
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.
- #1[disputed][awaiting moderator]in section: Entity Overview
“Nexera is a blockchain infrastructure project that rebranded from AllianceBlock in early 2023 following a series of adverse events.”
reviewerNexera rebranded from AllianceBlock in early 2023The cited rebrand announcement is dated February 2024, not 2023. The page's own timeline also places the NXRA all-time high in March 2024 under the new name.Proposed correction (not yet applied)Nexera is a blockchain infrastructure project that rebranded from AllianceBlock in early 2024 following a series of adverse events.
unverifiable
6 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #2[unverifiable][awaiting moderator]in section: Entity Overview
“AllianceBlock rebranded to the Nexera Foundation after the February 2023 BonqDAO incident forced the replacement of the original ALBT token with NXRA.”
reviewerBonqDAO incident forced replacement of ALBT with NXRA and caused the rebrandThe causal link is not in the cited rebrand source. The Medium statement was blocked/not read, so I could not confirm it elsewhere. - #3[unverifiable][awaiting moderator]in section: Entity Overview
“an ISO 27001-certified compliance platform called ComPilotAI”
reviewerISO 27001-certified ComPilotAI platformI did not verify the CoinMarketCap page, and the Defiant source does not mention the certification. - #4[unverifiable][awaiting moderator]in the timeline
“AllianceBlock launches Token Distribution Portal for NXRA, the replacement token for the affected ALBT, effectively rebranding as Nexera.”
reviewerTimeline entry sources a Nexera token distribution portal launch and rebrand to a BonqDAO statementThe cited URL is the BonqDAO hack statement, which is unlikely to describe a later NXRA portal launch, and the Defiant source dates the rebrand to Feb 2024. I could not confirm this entry from any source. - #6[unverifiable][awaiting moderator]in section: August 2024 Hack: Private Key Compromise via BeaverTail Malware
“The malware deployed was BeaverTail, an information stealer documented as part of North Korean state-backed threat actor toolkits.”
reviewerMalware deployed was BeaverTailBeaverTail is not named in the Halborn article. I could not read the post-mortem, and the page's summary states it as fact. The named malware family is not confirmed by sources I read. - #9[unverifiable][awaiting moderator]in section: Known Attacker On-Chain Addresses
“Exchanges including MEXC, Gate, Binance, Kraken, OKX, HTX, and HitBTC were used as alleged exit venues.”
reviewerExchanges named as exit venuesThe primary cited source names no exchanges. The Quadriga case study was not checked. Naming exchanges as exit venues without support is a risk to those entities. - #11[unverifiable][awaiting moderator]in section: Token Burn Mitigation and Market Impact
“stating the action would "prevent these tokens from being used, traded, or circulated, thereby protecting the integrity of the NXRA token's value."”
reviewerQuoted statement from the burn announcementThe quote was not found in the first-listed cited source. It may be in the CryptoNews or crypto.news articles, which I did not fetch.
link rot
1 claimA cited source no longer resolves or no longer says what the page attributes to it.
- #14[link rot][awaiting moderator]in the cited sources
“https://web.archive.org/web/20260724165133/https://www.coinspeaker.com/ftx-alameda-12-7b-lawsuit-cftc/”
reviewerArchive URL for the Coinspeaker source points to an unrelated articleThe archive_url is a Coinspeaker FTX/Alameda lawsuit article, not the Nexera burn article. I did not fetch the replacement snapshot, so it is taken from the page's own url field.Proposed correction (not yet applied)http://web.archive.org/web/20240901021215/https://www.coinspeaker.com/nexera-burns-32-5m-nxra-tokens/
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #7[partially supported][awaiting moderator]in the summary
“a threat actor later attributed to North Korea's Lazarus Group used social engineering and BeaverTail malware”
reviewerSummary states the actor was later attributed to Lazarus GroupThe summary reads as settled attribution, while the section body correctly says it is probabilistic. The BeaverTail name is also unconfirmed (see separate finding). - #12[partially supported][awaiting moderator]in section: Token Burn Mitigation and Market Impact
“The token price dropped over 40–53% on the day of the hack (from approximately $0.062 to $0.029–$0.036).”
reviewerPrice drop and recovery figuresThe percentage drops and recovery are supported. The exact dollar prices are not confirmed. The 'as of May 2026 ... down approximately 99% from ATH' claim relies on live CoinMarketCap data I did not check.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #5[confirmed][no action needed]in section: August 2024 Hack: Private Key Compromise via BeaverTail Malware
“Of the 47.24 million tokens stolen, approximately 14.75 million were sold for roughly $449,000 before the freeze.”
reviewerAttacker moved at ~05:05 UTC, sold at 05:28-05:29, contract paused 06:28 UTC; 47.24M NXRA taken; 14.75M sold for ~$449K; 32.5M remainedToken and dollar figures match two independent secondary sources. The intraday UTC times could not be checked because the primary post-mortem returned 403. - #8[confirmed][no action needed]in the summary
“limiting confirmed liquidated losses to roughly $449,000.”
reviewerValued at approximately $1.9 million; confirmed liquidated loss ~ $449,000Consistent with Halborn and the research repository. Headline press figures range from $1.5M to $1.8M. - #10[confirmed][no action needed]in section: Known Attacker On-Chain Addresses
“0xe697949817a45446776376db203c04d31b580a10”
reviewerAttacker addresses listedAddress labels match the source. I did not independently verify them on-chain. - #13[confirmed][no action needed]in section: Token Burn Mitigation and Market Impact
“Exchanges KuCoin and MEXC suspended NXRA trading immediately after the incident.”
reviewerExchanges suspended trading after the incidentSupported. Coinspeaker says all services (deposits, withdrawals, trading) were suspended.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.