Fact-check findings

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

1. #9[unverifiable][awaiting moderator]in section: Token Performance and Market Impact

   “Aperture Finance launched its native APTR token on May 31, 2024, with a reported initial valuation of $250 million following $12 million raised across multiple funding rounds.”

   reviewerAPTR launched May 31, 2024 at a $250M valuation; ATH about $0.12497 on June 10, 2024; down 99.25% in 2025I did not fetch the market-data pages, so the token dates and prices are not checked. The Medium source is unarchived. The summary also calls $250M a Series A valuation while this section calls it a token valuation, which is inconsistent.
   citedcoinmarketcap.com/currencies/aperture-finance/medium.com/@aperturefinance/aperture-fin…ptr-fca15735d698
2. #10[unverifiable][awaiting moderator]in section: Protocol Background and Funding

   “The founding team includes Lian Zhu, Gao Han, and Peiqian Li, whose professional backgrounds have been described in promotional materials as drawing from Google, Netflix, and Wall Street.”

   reviewerFounding team and promotional-background claimsI did not find a source for the named individuals. The page already hedges this as promotional material.
   citedchainbroker.io/projects/aperture-finance/
3. #11[unverifiable][awaiting moderator]in section: ZachXBT Flagging

   “Aperture LM has been flagged by on-chain investigator ZachXBT, though the specific content and date of ZachXBT's public statement regarding this entity could not be independently verified through publicly accessible primary sources at the time of this investigation.”

   reviewerZachXBT flagged Aperture LMNo ZachXBT flag appears in any exploit coverage I found. The section asserts a flag it admits it cannot source, and its heading is misleading.
   citedzachxbt.mirror.xyz/

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

1. #3[partially supported][awaiting moderator]in section: January 2026 Smart Contract Exploit

   “Security firm PeckShield first flagged the suspicious transactions publicly.”

   reviewerPeckShield first flagged the suspicious transactionsThe cited BlockSec source does not name PeckShield and says BlockSec raised its own alerts. Early reports may name PeckShield, but I did not verify that. Priority of first flag is unconfirmed.
   citedblocksec.com/blog/17m-closed-source-smar…swapnet-aperture
2. #4[partially supported][awaiting moderator]in section: January 2026 Smart Contract Exploit

   “and the primary attacker address identified was 0xe3e73f1e6ace2b27891d41369919e8f57129e8ea”

   reviewerThe primary attacker address was 0xe3e73f...The address appears in AMLBot, but described as a copycat or secondary wallet. BlockSec names no attacker address. The 'primary' label is overstated.
   citedblog.amlbot.com/13-5m-lost-in-aperture-f…chain-breakdown/
3. #5[partially supported][awaiting moderator]in section: Fund Laundering via Tornado Cash

   “deposited approximately 1,242.7 ETH (valued at approximately $2.4 million at the time) into Tornado Cash, structured in 10 ETH and 100 ETH increments to obscure the trail.”

   reviewerAbout 1,242.7 ETH (~$2.4M) was deposited into Tornado Cash in 10 and 100 ETH incrementsThe 1,242 ETH figure is corroborated by a secondary report only. The AMLBot page cited does not state it. The cited MEXC page is gone, and I did not verify the increment detail.
   citedwww.mexc.com/news/643634blog.amlbot.com/13-5m-lost-in-aperture-f…chain-breakdown/

The cited evidence supports the claim as written.

1. #1[confirmed][no action needed]in the timeline

   “Same attacker simultaneously exploits SwapNet for ~$13.4 million; combined losses reach ~$17 million.”

   reviewerAperture losses were about $3.67M and SwapNet about $13.4M, combined about $17M, on Jan 25, 2026Figures match BlockSec. AMLBot's headline uses $13.5M, which is a different scope but not a contradiction.
   citedblocksec.com/blog/17m-closed-source-smar…swapnet-aperture
2. #2[confirmed][no action needed]in section: January 2026 Smart Contract Exploit

   “The root cause was an arbitrary-call vulnerability in the protocol's V3/V4 helper module (function 0x67b34120 / internal function 0x1d33).”

   reviewerRoot cause was an arbitrary-call flaw in function 0x67b34120 / internal 0x1d33, with the victim and attack contract addresses givenSelector and addresses match BlockSec.
   citedblocksec.com/blog/17m-closed-source-smar…swapnet-aperture
3. #6[confirmed][no action needed]in section: Fund Laundering via Tornado Cash

   “AMLBot's on-chain forensic analysis identified cross-chain bridging from Base to Ethereum Mainnet via Relay Protocol and Superbridge as a secondary laundering step.”

   reviewerAMLBot found Base to Ethereum bridging via Relay and Superbridge, and a link to the Li.Fi/Jumper exploiterSupported. The Li.Fi link is AMLBot's own clustering and not independently verified.
   citedblog.amlbot.com/13-5m-lost-in-aperture-f…chain-breakdown/
4. #7[confirmed][no action needed]in section: Closed-Source Contracts and Audit Gaps

   “Aperture Finance's published security audit page documents six historical audits”

   reviewerAperture's audit page lists six audits, the last in September 2023The list and dates match. The 2022 Oak audit completion dates (3/8, 6/27, 9/24) are consistent with the timeline entries.
   citeddocs.aperture.finance/docs/transparency/security-audit
5. #8[confirmed][no action needed]in section: Team Response and User Remediation

   “no formal public compensation plan for affected users has been confirmed, and the promised post-mortem had not been publicly verified as published in detail.”

   reviewerAperture has not confirmed compensation, and the post-mortem was not verified as publishedNo compensation or post-mortem found. The claim is hedged, so it is consistent with what I found.
   citedcoinfomania.com/aperture-finance-reports…o-revoke-access/