Skip to main content
AVOID.NET
← Hector Lendingreviewed 2026-11-02 · 10 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Hector Lending 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.

unverifiable 4partially supported 2confirmed 40 corrections pending · 0 applied

unverifiable

4 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #2[unverifiable][awaiting moderator]in section: Security Incidents and Exploits
    “In total, direct security losses across the ecosystem are estimated at approximately $40 million when combined with the $8 million lost due to the Multichain bridge collapse in July 2023.”
    reviewerDirect security losses across the ecosystem are about $40 million including $8 million from Multichain.The incidents named on the page total about $11.4M ($653K + $2.7M + $8M). No source found for $40M, and it conflicts with the page's own figures.
  2. #8[unverifiable][awaiting moderator]in section: Protocol Overview and History
    “As of 2024, DefiLlama reports Hector Lending's TVL at approximately $7,600 with zero active loans, reflecting its complete operational collapse.”
    reviewerHector Lending TVL about $7,600 with zero active loans as of 2024.DefiLlama returned 403; the figure is a live metric that changes over time, so a 2024 snapshot is not checkable.
  3. #9[unverifiable][awaiting moderator]in section: Alleged Treasury Mismanagement and Slow Rug Accusations
    “When the January 2024 hack occurred, the team's last communication to investors was on January 18, 2024, after which they went silent, allegedly deleting the Google Group email address that had served as their sole remaining communication channel.”
    reviewerTeam's last communication to investors was Jan 18, 2024, then deleted the Google Group.I did not fetch the Cointelegraph article, and the other sources do not give the date. The wording is hedged as 'allegedly'.
  4. #10[unverifiable][awaiting moderator]in the timeline
    “BVI courts issue final receivership order appointing Interpath on a full and final basis.”
    reviewerFinal BVI receivership order on April 9, 2024.DL News expected finalisation on March 12; the April 9 date was not independently confirmed (offshorealert not fetched).

partially supported

2 claims

The cited evidence supports part of the claim but not all of it.

  1. #1[partially supported][awaiting moderator]in section: Security Incidents and Exploits
    “Blockchain analysis suggests the January 2024 exploit was either an inside job or a private key compromise, as the attacker had access to the team's deployer account.”
    reviewerBlockchain analysis suggests the January 2024 exploit was an inside job or private key compromise, as the attacker had access to the team's deployer account.Source lists the category but does not confirm an inside job or key leak, and does not say the attacker had deployer access. Page overstates.
  2. #3[partially supported][awaiting moderator]in section: Security Incidents and Exploits
    “The third and most financially damaging incident — though it affected the redemption contract rather than Hector Lending directly — occurred on January 15, 2024.”
    reviewerThe January 2024 redemption-contract exploit was the most financially damaging incident.$2.7M is larger than the $653K bridge exploit but smaller than the $8M Multichain loss on the same page. It is the largest of the three listed hacks only.

confirmed

4 claims

The cited evidence supports the claim as written.

  1. #4[confirmed][no action needed]in section: Security Incidents and Exploits
    “A $2.7 million loss resulted from exploitation of the HectorRedemptionTreasury contract, a smart contract deployed to distribute liquidation proceeds to token holders.”
    reviewerJan 15, 2024 exploit: $2.7M, tx 0x1b813d9 and 0xd1b342c, CertiK audit Dec 19, 2023, finding acknowledged but unresolved.Matches the CertiK post-mortem.
  2. #5[confirmed][no action needed]in section: Rage Quit Vote and Receivership
    “On February 19, 2024, the Eastern Caribbean Supreme Court (British Virgin Islands) issued an order placing Hector Network into receivership and appointing Interpath BVI — with directors James Drury and Paul Pretlove — as interim receivers.”
    reviewerEastern Caribbean Supreme Court receivership order on Feb 19, 2024; Interpath BVI with Drury and Pretlove; $9.3M assets in a new Gnosis Safe.Confirmed. The 'controlled exclusively by Interpath employees' detail was not checked.
  3. #6[confirmed][no action needed]in section: Rage Quit Vote and Receivership
    “On July 15, 2023, Hector Network token holders voted with 83.31% support in favor of dissolving the project and liquidating its remaining treasury assets via governance proposal HIP 42.”
    reviewerHIP 42 passed July 15, 2023 with 83.31%.Supported by DefiLlama governance data (search snippet), not by the cited DL News article. The vote ran July 15-17, so the timeline's 'pass' on 07-15 is approximate.
  4. #7[confirmed][no action needed]in the timeline
    “U.S. Bankruptcy Judge Michael B. Kaplan grants Chapter 15 recognition of the BVI receivership, marking the first time a DAO has obtained US bankruptcy recognition as a debtor.”
    reviewerJudge Kaplan granted Chapter 15 recognition on July 15, 2024, the first DAO to obtain it.Consistent with Bloomberg Law and GRR headline.
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.