Fact-check findings

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

1. #1[disputed][awaiting moderator]in section: August 2023 Vault Drain Exploit

   “The incident occurred the same week as a separate exploit on the Exactly Protocol (BNB Chain), with which it was confirmed to be unrelated by blockchain security firms DeDotFi and PeckShield.”

   reviewerDeDotFi and PeckShield confirmed the Harbor exploit was unrelated to the Exactly Protocol attackNeither fetched source attributes a confirmation of non-relation to DeDotFi or PeckShield.
   Proposed correction (not yet applied)

   The incident occurred the same week as a separate exploit on the Exactly Protocol (BNB Chain); reporting describes the two attacks as separate.
   citedtherecord.media/millions-stolen-exactly-…i-cryptocurrencywww.bitdegree.org/crypto/news/over-7m-st…actly-and-harbor
2. #2[disputed][awaiting moderator]in the timeline

   “Blockchain security firms DeDotFi and PeckShield confirm the Harbor exploit is unrelated to a concurrent Exactly Protocol attack on BNB Chain.”

   reviewerTimeline: DeDotFi and PeckShield confirmed unrelated (same defect)Same unsupported attribution as in the section text.
   Proposed correction (not yet applied)

   Harbor exploit is reported as separate from a concurrent Exactly Protocol attack on BNB Chain.
3. #3[disputed][awaiting moderator]in section: Risk Profile and Trust Assessment

   “ZachXBT, the pseudonymous on-chain investigator known for tracing stolen crypto funds, has flagged Harbor Protocol as a point of concern within the context of DeFi exploit tracking.”

   reviewerZachXBT flagged Harbor Protocol as a point of concernNo fetched source ties ZachXBT to Harbor; the Wikipedia citation is a generic biography.
   Proposed correction (not yet applied)

   ZachXBT is a pseudonymous on-chain investigator known for tracing stolen crypto funds.
   citeden.wikipedia.org/wiki/ZachXBTtherecord.media/millions-stolen-exactly-…i-cryptocurrency

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

1. #4[unverifiable][awaiting moderator]in section: August 2023 Vault Drain Exploit

   “The attacker's on-chain address was identified as comdex1sma0ntw7fq3fpux8suxkm9h8y642fuqt0ujwt5.”

   reviewerAttacker address identified as comdex1sma0n...Address not found in fetched sources; the Comdex post-mortem was unreachable. Naming an address as the attacker is a sensitive claim.
   citedwww.web3isgoinggreat.com/?id=harbor-protocol-exploit
2. #7[unverifiable][awaiting moderator]in section: June 2023 Oracle Incident

   “The root cause was a sudden spike in trading volume on ShadeSwap following the protocol's listing on CoinGecko.”

   reviewerJune 2023 oracle incident from CoinGecko VWAP and ShadeSwap volume; stATOM priced at $0.02Primary report unreachable; details of mechanism and prices not independently checked. June incident existence confirmed.
   citedblog.comdex.one/harbor-protocol-oracle-i…port-654ff67b25b
3. #9[unverifiable][awaiting moderator]in section: Risk Profile and Trust Assessment

   “No independent security audit from a major firm (Halborn, Certik, Trail of Bits) has been identified in open-source search results for Harbor Protocol's smart contracts.”

   reviewerNo independent audit identifiedAbsence claim; not checked exhaustively. Comdex has an Immunefi bounty page, which suggests some security program exists.

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

1. #5[partially supported][awaiting moderator]in section: August 2023 Vault Drain Exploit

   “Total losses were estimated at approximately $250,000–$289,000 based on the TVL drop from roughly $370,000 to approximately $81,000 as recorded by DefiLlama.”

   reviewerTotal losses approx $250,000-$289,000 from TVL drop from ~$370,000 to ~$81,000TVL figures confirmed; $250k matches DefiLlama's hack entry, $289k upper bound not verified (370-81 = 289).
   citeddefillama.com/protocol/harbor-protocol
2. #8[partially supported][awaiting moderator]in section: Token Performance and Protocol Decline

   “The protocol was never listed on a major centralized exchange. The HARBOR token had no exchange listing at the time of the exploit, and secondary market liquidity was extremely thin.”

   reviewerProtocol was never listed on any exchange / HARBOR had no exchange listingInternally inconsistent: the page also cites a Coinbase price page and says the June incident followed a CoinGecko listing and ShadeSwap trading, implying DEX listings existed. Not resolved against a fetched source.
   citedwww.coincarp.com/currencies/harbor-protocol/
3. #11[partially supported][awaiting moderator]in section: Risk Profile and Trust Assessment

   “Third, post-exploit TVL collapsed to zero and has not recovered, indicating the protocol has effectively ceased operations without a formal shutdown announcement or structured wind-down.”

   reviewerTVL collapsed to zero immediately after the exploitPost-exploit TVL was about $81k; the $0 figure came later (reported as of June 2025). The summary's phrasing 'collapsed to effectively zero' after the incidents compresses this.
   citeddefillama.com/protocol/harbor-protocol

The cited evidence supports the claim as written.

1. #6[confirmed][no action needed]in section: August 2023 Vault Drain Exploit

   “Harbor Protocol issued a public appeal to the attacker to make contact, saying the team was 'open to talk to find a solution that is optimal and doesn't impact users and community members.'”

   reviewerExploit announced August 19, 2023; community quote and appeal to attackerAppeal and affected vaults match The Record.
   citedtherecord.media/millions-stolen-exactly-…i-cryptocurrency
2. #10[confirmed][no action needed]in section: Token Performance and Protocol Decline

   “DefiLlama reports Harbor Protocol's current TVL as $0, consistent with protocol inactivity following the August 2023 exploit.”

   reviewerTVL currently $0 and protocol inactiveSupported by search snippet only.
   citeddefillama.com/protocol/harbor-protocol