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. #4[disputed][awaiting moderator]in section: June 2025 Exploit — Unreleased Leverage Contract

   “Silo's real-time monitoring partner Hypernative Labs detected malicious activity 3 minutes and 20 seconds before the exploit was executed but was unable to prevent it.”

   reviewerSilo's real-time monitoring partner Hypernative Labs detected malicious activity 3 minutes and 20 seconds before the exploit was executed but was unable to prevent it.The page conflates two different firms. The '3 minutes 20 seconds before the exploit' detection is attributed by press coverage to PeckShield, while Certora's own published timeline shows Hypernative's flag came 18 minutes after the first attack, not before it.
   Proposed correction (not yet applied)

   PeckShield's threat intelligence system detected malicious activity 3 minutes and 20 seconds before the exploit was executed but was unable to prevent it.
   citedsilofinance.medium.com/post-mortem-unrel…itd-0ab8f37afcbbsmartcontractshacking.com/hacks/silo-finance-hack-2025
2. #5[disputed][awaiting moderator]in section: On-Chain Attribution and Fund Laundering

   “Blockchain security firm PeckShield flagged that the attacker wallet was funded via Tornado Cash prior to the exploit, through a funding transaction traceable to address 0xb8567f70d61c070ac298ae9924bacdaac8bdbec8c7d71fa0e5d2fab030ddf035.”

   reviewerPeckShield traced the attacker's funding to a Tornado Cash transaction at address 0xb8567f70d61c070ac298ae9924bacdaac8bdbec8c7d71fa0e5d2fab030ddf035.The 64-hex-character string given is 32 bytes long, which is the format of an Ethereum transaction hash, not a 20-byte (40-hex-character) address — it cannot be a wallet address as labeled. No source found corroborates this value in any form, suggesting it was fabricated or garbled during drafting. The underlying general claim (Tornado Cash funding) is independently supported, so only the specific address is removed.
   Proposed correction (not yet applied)

   Blockchain security firm PeckShield flagged that the attacker wallet was funded via Tornado Cash prior to the exploit.
   citedwww.quillaudits.com/blog/hack-analysis/h…inance-lost-500kwww.cryptopolitan.com/silo-finance-hacke…n-loss-reported/
3. #10[disputed][awaiting moderator]in section: Protocol Overview

   “The SILO governance token has a maximum supply of one billion, vested over four years, with 45% allocated to a community treasury managed by SiloDAO.”

   reviewerThe SILO token has a maximum supply of one billion, vested over four years, with 45% allocated to a community treasury managed by SiloDAO.The sentence structure implies the community treasury's 45% vests over four years; independent sources put that specific allocation's vesting at three years, with the four-year figure describing the token's overall emission schedule instead.
   Proposed correction (not yet applied)

   The SILO governance token has a maximum supply of one billion, minted over four years, with 45% allocated to a community treasury managed by SiloDAO that vests over three years.
   citedsilopedia.silo.finance/silodao/usdsilo/t…tion-and-vesting

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

1. #12[unverifiable][awaiting moderator]in section: Protocol Overview

   “As of mid-2025, Silo V2 was ranked among the top 50 lending protocols by TVL on DeFiLlama.”

   reviewerAs of mid-2025, Silo V2 was ranked among the top 50 lending protocols by TVL on DeFiLlama.Plausible given the number of lending protocols tracked, but I could not independently confirm a specific top-50 ranking for the mid-2025 period from the live or cached DeFiLlama pages I could access.
   citeddefillama.com/protocol/silo-v2
2. #13[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Scrutiny

   “ZachXBT, an independent on-chain investigator known for tracking DeFi exploits and scams, flagged Silo Finance in connection with the June 2025 exploit.”

   reviewerZachXBT flagged Silo Finance in connection with the June 2025 exploit.None of the three sources cited for this section mention ZachXBT at all, and a targeted web search for ZachXBT plus Silo Finance returned no corroborating result. The page's own hedge ('has not been independently verified through a publicly archived primary source') is accurate, but the underlying premise that a flag occurred at all could not be confirmed from any source, including the ones cited.
   citedwww.cryptopolitan.com/silo-finance-hacke…n-loss-reported/phemex.com/news/article/silo-finance-exp…-545k-loss-11097www.ainvest.com/news/silo-finance-loses-…e-drops-11-2506/

The claim was accurate when written but events since have overtaken it.

1. #8[stale][awaiting moderator]in section: Security Posture and Audit History

   “running an Immunefi bug bounty program with rewards of up to $350,000 for critical vulnerabilities on V2 and V3”

   reviewerImmunefi runs a Silo Finance V2/V3 bug bounty program with rewards up to $350,000 for critical vulnerabilities.This was true at an earlier point in 2026 but the bounty program's cap has since been reduced; the page's figure is now out of date.
   Proposed correction (not yet applied)

   running an Immunefi bug bounty program with rewards of up to $100,000 for critical vulnerabilities on V2 and V3
   citedimmunefi.com/bug-bounty/silofinance-v2/information/

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

1. #11[partially supported][awaiting moderator]in section: Protocol Overview

   “as well as an xSILO revenue-sharing token that distributes 50% of monthly DAO revenue to stakers”

   reviewerxSILO distributes 50% of monthly DAO revenue to stakers.50% revenue share to xSILO holders is well corroborated; a specifically 'monthly' distribution cadence was not found in any source checked, so that detail is unconfirmed rather than contradicted.
   citeddocs.silo.finance/
2. #15[partially supported][awaiting moderator]in section: Market and Token Impact

   “Following public disclosure of the June 25, 2025 exploit, the SILO governance token dropped approximately 11% within 24 hours, falling to approximately $0.04035 according to CoinGecko data.”

   reviewerSILO token dropped ~11% within 24 hours to approximately $0.04035, with 14-day RSI below 36 and 50-day moving average around $0.055 at the time of the exploit.The headline price-drop figures (11%, ~$0.04035) are corroborated by multiple independent outlets. The RSI<36 and 50-day moving average figures rest on a single source I could not independently verify (site returned 403), so the claim is only partially supported.
   citedwww.ainvest.com/news/silo-finance-loses-…e-drops-11-2506/

The cited evidence supports the claim as written.

1. #1[confirmed][no action needed]in section: June 2025 Exploit — Unreleased Leverage Contract

   “On June 25, 2025, at 14:11:23 UTC, a targeted exploit drained 224 ETH (approximately $545,000) from a peripheral smart contract that the Silo core team had deployed to mainnet for internal testing of an unreleased leverage feature.”

   reviewerThe June 25, 2025 exploit occurred at 14:11:23 UTC and drained 224 ETH (~$545,000) from an unreleased peripheral leverage contract deployed to mainnet for internal testing.Corroborated by both the primary incident responder (Certora) and an independent security-research writeup.
   citedsilofinance.medium.com/post-mortem-unrel…itd-0ab8f37afcbbwww.certora.com/blog/silo-incident-repor…contract-exploit
2. #2[confirmed][no action needed]in section: June 2025 Exploit — Unreleased Leverage Contract

   “The affected contract, LeverageUsingSiloFlashloanWithGeneralSwap, exposed an openLeveragePosition function that accepted a user-controlled _swapArgs parameter without adequate whitelisting or validation.”

   reviewerThe affected contract was LeverageUsingSiloFlashloanWithGeneralSwap, exploited via an unvalidated openLeveragePosition/_swapArgs call that let the attacker borrow against a team wallet's approvals and route proceeds to itself.Core mechanism is corroborated by two independent technical analyses; minor variation in how deeply each explains the root cause but no contradiction of the page's account.
   citedwww.quillaudits.com/blog/hack-analysis/h…inance-lost-500ksmartcontractshacking.com/hacks/silo-finance-hack-2025
3. #3[confirmed][no action needed]in section: June 2025 Exploit — Unreleased Leverage Contract

   “setting the receiver to the attacker's own address (0x04377cfaf4b4a44bb84042218cdda4cebcf8fd62)”

   reviewerThe attacker wallet is 0x04377cfaf4b4a44bb84042218cdda4cebcf8fd62.Matches independently reported attacker address.
   citedwww.quillaudits.com/blog/hack-analysis/h…inance-lost-500k
4. #6[confirmed][no action needed]in section: On-Chain Attribution and Fund Laundering

   “Notably, PeckShield further identified that on the same day as the Silo exploit (June 25, 2025), the attacker address was linked to wallets that had previously drained approximately $12 million from Cork Protocol in a separate incident on May 28, 2025.”

   reviewerPeckShield identified that the Silo attacker address was linked to wallets that had previously drained ~$12 million from Cork Protocol on May 28, 2025.Consistent with press reporting; page's own hedged language ('alleged connection... implies') matches the uncertainty in the underlying source.
   citedwww.cryptopolitan.com/silo-finance-hacke…n-loss-reported/
5. #7[confirmed][no action needed]in section: On-Chain Attribution and Fund Laundering

   “In that incident, the Cork Protocol exploiter stole 3,761 wstETH by targeting the wstETH:weETH market, and subsequently laundered a total of approximately 4,520 ETH (roughly $11 million) through Tornado Cash.”

   reviewerCork Protocol was exploited on May 28, 2025 for approximately $12 million (3,761 wstETH) via the wstETH:weETH market.Figures match independent primary (Cork post-mortem) and secondary (PeckShield-sourced) reporting.
   citedwww.bitget.com/news/detail/12560604835357
6. #9[confirmed][no action needed]in section: Security Posture and Audit History

   “Certora stated that had formal verification been performed on the leverage module, the problematic user-controlled external call would have been identified.”

   reviewerCertora's post-mortem acknowledged that its Prover was not applied to the exploited leverage contract, and that formal verification would have caught the bug.Direct match to the primary source, which is Certora's own first-party incident report.
   citedwww.certora.com/blog/silo-incident-repor…contract-exploit
7. #14[confirmed][no action needed]in section: Security Posture and Audit History

   “The protocol also experienced an earlier security event in May 2023, when a whitehat disclosed via Immunefi a critical interest rate model vulnerability (IRMV1) that could have exposed approximately $3 million in Ethereum-market deposits. The whitehat was awarded 100,000 USDC. A patched model (IRMv2) was deployed by May 1, 2023.”

   reviewerIn May 2023, a whitehat disclosed via Immunefi a critical interest rate model vulnerability (IRMV1) that could have exposed ~$3 million in Ethereum-market deposits, was awarded 100,000 USDC, and a patched model (IRMv2) was deployed by May 1, 2023.Core facts (vulnerability type, ~$3M exposure estimate, 100,000 USDC bounty) are corroborated by multiple secondary reports; precise day-level dates in the timeline are plausible but not independently confirmed, and no contradicting source was found.
   citedmedium.com/immunefi/silo-finance-logic-e…iew-35de29bd934amedium.com/silo-protocol/vulnerability-d…-06-c1dfd4c4dbb8