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. #11[disputed][awaiting moderator]in section: The Kiln Supply Chain Hack ($41M)

   “Kiln's own post-mortem noted that the customer 'failed to decode the transaction before signing,' which Kiln identified as a best-practice gap.”

   reviewerKiln's own post-mortem noted that the customer 'failed to decode the transaction before signing,' which Kiln identified as a best-practice gap.This is presented as a direct quotation from Kiln's post-mortem, but the exact phrase does not appear there; it is a fabricated/misattributed quote built from Kiln's general decoding-advice language.
   Proposed correction (not yet applied)

   Kiln's own post-mortem states that it has 'consistently recommended that customers decode transactions to verify their integrity before signing,' and that the malicious transaction 'was approved by a quorum of signatories in the customer's custody instance' — a general best-practice reminder, not a direct statement blaming the customer.
   citedwww.kiln.fi/post/re-enablement-of-kiln-s…dent-information
2. #12[disputed][awaiting moderator]in section: Security Posture

   “Kiln's own post-mortem explicitly identified failure to decode the full transaction prior to signing as a best-practice gap on the part of its enterprise customer — implicating SwissBorg's internal custody review procedures.”

   reviewerKiln's own post-mortem explicitly identified failure to decode the full transaction prior to signing as a best-practice gap on the part of its enterprise customer.Second occurrence of the same overstated attribution to Kiln's post-mortem, here used to support a stronger editorial conclusion ('implicating SwissBorg's internal custody review procedures') than the source supports.
   Proposed correction (not yet applied)

   Kiln's own post-mortem described decoding transactions before signing as a best practice it has 'consistently recommended' to customers, without explicitly attributing the incident to a failure in its enterprise customer's custody review procedures.
   citedwww.kiln.fi/post/re-enablement-of-kiln-s…dent-information
3. #20[disputed][awaiting moderator]in the timeline

   “2026-03-11”

   reviewerBlocknodes SAS received MiCA authorization from the AMF specifically on March 11, 2026.The page's timeline date appears to reflect the press-announcement date rather than the actual regulatory grant date recorded in the official MiCA register.
   Proposed correction (not yet applied)

   2026-03-05
   citedswissborg.com/blog/swissborg-secures-mic…-from-french-amf
4. #23[disputed][awaiting moderator]in section: User Protections

   “with CEO Cyrus Fazel publicly stating 'SwissBorg community will not take a loss. Any gap in recovered funds will be covered.'”

   reviewerCEO Cyrus Fazel publicly stated 'SwissBorg community will not take a loss. Any gap in recovered funds will be covered.'The quotation marks present this as a verbatim statement, but it misquotes the cited source on two words ('community' for 'users', and an inserted 'in recovered funds').
   Proposed correction (not yet applied)

   with CEO Cyrus Fazel publicly stating 'SwissBorg users will not take a loss. Any gap will be covered.'
   citedswissborg.com/blog/sol-earn-incident-swissborg-recovery

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

1. #2[unverifiable][awaiting moderator]in section: Background

   “Fazel and Lesoismier both hold backgrounds at EDHEC Business School and spent over a decade in European wealth management before founding SwissBorg.”

   reviewerFazel and Lesoismier both hold backgrounds at EDHEC Business School and spent over a decade in European wealth management before founding SwissBorg.No independent biography search surfaced EDHEC Business School or a specific decade-plus wealth-management tenure for either founder. Not contradicted, but not corroborated either.
2. #18[unverifiable][awaiting moderator]in section: Regulatory Status

   “SwissBorg is also a member of VQF (Verein zur Qualitätssicherung der Finanzdienstleister), a self-regulatory organization (SRO) recognized and supervised by the Swiss Financial Market Supervisory Authority (FINMA).”

   reviewerSwissBorg is a member of VQF, a FINMA-recognized self-regulatory organization, subjecting it to Swiss AML requirements without constituting a full FINMA banking/securities license.The cited SwissBorg help-center page returned HTTP 403 when fetched directly, so the claim could not be checked against its own primary source; only a weak secondary source corroborates VQF membership, and the characterization of VQF's relationship to FINMA is independently accurate.
   citedhelp.swissborg.com/hc/en-gb/articles/360…ion-and-licenses
3. #21[unverifiable][awaiting moderator]in section: Regulatory Status

   “Under the authorization, Blocknodes SAS is permitted to offer crypto custody, order execution, asset transfers, portfolio management, and investment advice.”

   reviewerUnder the MiCA authorization, Blocknodes SAS is permitted to offer crypto custody, order execution, asset transfers, portfolio management, and investment advice.Plausible and consistent with secondary press coverage, but not independently confirmable against the authoritative register's category-level detail.
   citednews.bitcoin.com/swissborg-secures-mica-…vices-across-eu/
4. #25[unverifiable][awaiting moderator]in section: User Protections

   “There is no publicly disclosed third-party insurance policy for digital assets stored in hot or warm infrastructure. The company references cold wallet insurance in marketing materials, but specific coverage amounts and underwriters are not disclosed.”

   reviewerThere is no publicly disclosed third-party insurance policy for digital assets stored in hot or warm infrastructure; cold wallet insurance is referenced in marketing without disclosed coverage amounts or underwriters.This is an absence claim (no disclosed policy found); it is consistent with the sources reviewed for this page, but a negative cannot be fully confirmed, only not contradicted.

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

1. #3[partially supported][awaiting moderator]in section: Background

   “As of 2024 the platform reported over one million registered users in 47 countries across 16 fiat currencies.”

   reviewerAs of 2024 SwissBorg reported over one million registered users in 47 countries across 16 fiat currencies.The user-count and fiat-currency figures match the cited source; the '47 countries' figure could not be found in the cited source or elsewhere, so it is unverified rather than contradicted.
   citeden.cryptonomist.ch/2024/07/23/swissborg-…pen-to-everyone/
2. #4[partially supported][awaiting moderator]in section: Background

   “routes trades across more than 12 centralized and decentralized exchanges via a Smart Engine to obtain best-available prices”

   reviewerSwissBorg's Smart Engine routes trades across more than 12 centralized and decentralized exchanges.The exchange count fluctuates by source and date (11-12); 'more than 12' is a minor overstatement rather than a material misrepresentation.
3. #14[partially supported][awaiting moderator]in section: The Kiln Supply Chain Hack ($41M)

   “The company engaged blockchain analytics firm Chainalysis, independent researcher ZachXBT, the SEAL security organization, and Fireblocks, in addition to notifying law enforcement.”

   reviewerThe company engaged blockchain analytics firm Chainalysis, independent researcher ZachXBT, the SEAL security organization, and Fireblocks, in addition to notifying law enforcement.Chainalysis, ZachXBT and law-enforcement notification are independently confirmed. No source found names 'SEAL' or Fireblocks as parties SwissBorg specifically engaged; the Fireblocks source cited elsewhere on the page does not mention SwissBorg at all.
   citedtherecord.media/swissborg-platform-solan…ocurrency-stolenwww.fireblocks.com/blog/case-for-native-…ng-kiln-incident
4. #15[partially supported][awaiting moderator]in the timeline

   “SwissBorg publicly confirms the breach. CEO Cyrus Fazel pledges full user reimbursement from treasury. SOL Earn redemptions suspended. Chainalysis, ZachXBT, SEAL, and Fireblocks engaged.”

   reviewerSwissBorg publicly confirms the breach on September 9, 2025; CEO pledges reimbursement; SOL Earn redemptions suspended; Chainalysis, ZachXBT, SEAL, and Fireblocks engaged.Timeline duplicate of the same unverified SEAL/Fireblocks engagement claim found in the narrative section.
   citedtherecord.media/swissborg-platform-solan…ocurrency-stolen

The cited evidence supports the claim as written.

1. #1[confirmed][no action needed]in section: Background

   “SwissBorg was founded in 2017 by Cyrus Fazel (CEO) and Anthony Lesoismier (CSO), both formerly of traditional wealth management and banking.”

   reviewerSwissBorg was founded in 2017 in Lausanne, Switzerland, by Cyrus Fazel (CEO) and Anthony Lesoismier (CSO).Core founding facts are independently corroborated by Wikipedia and CoinDesk.
   citedhelp.swissborg.com/hc/en-gb/articles/360…hat-is-SwissBorgwww.venturelab.swiss/SwissBorg-CEO-Cyrus…stment-interests
2. #5[confirmed][no action needed]in section: The Kiln Supply Chain Hack ($41M)

   “On September 8, 2025, an attacker drained approximately 192,600 SOL (valued at roughly $41.5 million) from an external DeFi wallet used to operate SwissBorg's SOL Earn staking strategy.”

   reviewerOn September 8, 2025, an attacker drained approximately 192,600 SOL (~$41.5 million) from an external DeFi wallet used for SwissBorg's SOL Earn staking strategy.Figures and date are consistent across Kiln's own disclosure and multiple independent outlets.
   citedwww.kiln.fi/post/re-enablement-of-kiln-s…dent-informationprotos.com/swissborg-ceo-blames-41m-loss…ng-partner-kiln/
3. #6[confirmed][no action needed]in section: The Kiln Supply Chain Hack ($41M)

   “Using this token, the attacker triggered CI/CD pipeline workflows by creating and rapidly deleting branches designed to avoid automated detection. From those workflows, the attacker harvested cloud credentials spanning AWS, GCP, and bare-metal infrastructure.”

   reviewerThe attacker used a stolen GitHub token to trigger CI/CD workflows via rapidly created and deleted branches, then harvested AWS, GCP and bare-metal cloud credentials.Matches Kiln's own technical disclosure closely.
   citedwww.kiln.fi/post/re-enablement-of-kiln-s…dent-information
4. #7[confirmed][no action needed]in section: The Kiln Supply Chain Hack ($41M)

   “This access was used to inject a malicious payload directly into a running Kubernetes pod hosting the Kiln Connect API.”

   reviewerThe attacker injected a malicious payload into a running Kubernetes pod hosting the Kiln Connect API, modifying the 'deactivate stake' endpoint to return a second, malicious transaction reassigning withdrawal authority for stake accounts over 150,000 SOL.Confirmed directly against the primary post-mortem.
   citedwww.kiln.fi/post/re-enablement-of-kiln-s…dent-information
5. #8[confirmed][no action needed]in section: The Kiln Supply Chain Hack ($41M)

   “On August 31, SwissBorg used the Kiln Dashboard to unstake approximately 975 SOL.”

   reviewerOn August 31, 2025, SwissBorg used the Kiln Dashboard to unstake approximately 975 SOL, during which a malicious transaction silently reassigned withdrawal authority on high-value stake accounts.The date and mechanism are confirmed by Kiln itself; the precise 975 SOL figure rests on a secondary technical analysis, which is corroborating but not primary.
   citedharrydonnelly.substack.com/p/swissborgki…xploit-breakdown
6. #9[confirmed][no action needed]in section: The Kiln Supply Chain Hack ($41M)

   “Eight days later, on September 8 at approximately 12:02 UTC, the attacker executed the theft across eight separate transactions in under three minutes, draining all stake accounts whose withdrawal authority had been silently reassigned.”

   reviewerOn September 8 at approximately 12:02 UTC, the attacker executed the theft across eight separate transactions in under three minutes.Kiln's own post-mortem confirms only the date; the precise timing detail rests on independent on-chain analysis, which is credible and not contradicted elsewhere.
   citedharrydonnelly.substack.com/p/swissborgki…xploit-breakdown
7. #10[confirmed][no action needed]in section: The Kiln Supply Chain Hack ($41M)

   “Approximately 189,524 SOL was parked in a single attacker-controlled wallet, with roughly 3,000 SOL routed through exchanges including Bitget in a apparent liquidity test.”

   reviewerApproximately 189,524 SOL was parked in a single attacker-controlled wallet, with roughly 3,000 SOL routed through exchanges including Bitget as a liquidity test.Confirmed by two independent on-chain write-ups.
   citedharrydonnelly.substack.com/p/swissborgki…xploit-breakdown
8. #13[confirmed][no action needed]in section: The Kiln Supply Chain Hack ($41M)

   “CEO Cyrus Fazel characterized the incident as an attack on a counterparty, stating 'this was not a breach of the SwissBorg platform.'”

   reviewerSwissBorg CEO Cyrus Fazel characterized the incident as an attack on a counterparty, stating 'this was not a breach of the SwissBorg platform.'Quote verified verbatim against an independent outlet.
   citedprotos.com/swissborg-ceo-blames-41m-loss…ng-partner-kiln/
9. #16[confirmed][no action needed]in section: The Kiln Supply Chain Hack ($41M)

   “Kiln publicly disclosed the incident on October 7, 2025, after completing initial forensics with Sygnia, and announced six remediation measures: zero-trust access controls, hardened CI/CD pipelines, blast-radius isolation, container hardening, 24/7 monitoring, and enhanced validator key protection.”

   reviewerKiln publicly disclosed the incident on October 7, 2025, after forensics with Sygnia, announcing six remediation measures.Confirmed directly against the primary source.
   citedwww.kiln.fi/post/re-enablement-of-kiln-s…dent-information
10. #17[confirmed][no action needed]in section: Regulatory Status

    “The primary operating entity, SwissBorg Solutions OÜ, holds a Virtual Currency Service License (FVT000326) issued by the Financial Intelligence Unit (FIU) of Estonia, and was registered with France's Autorité des Marchés Financiers (AMF) under number E2022-034 as a Digital Asset Service Provider (DASP).”

    reviewerSwissBorg Solutions OÜ holds a Virtual Currency Service License (FVT000326) issued by Estonia's FIU, and was registered with France's AMF under number E2022-034 as a DASP.AMF number confirmed against AMF's own public register. Estonian license number rests on a secondary French-language source rather than the Estonian FIU register directly.
    citedhelp.swissborg.com/hc/en-gb/articles/360…ion-and-licenses
11. #19[confirmed][no action needed]in section: Regulatory Status

    “In March 2026, SwissBorg's French entity Blocknodes SAS received full MiCA (Markets in Crypto-Assets Regulation) authorization from the AMF — one of Europe's most demanding financial regulators.”

    reviewerIn March 2026, SwissBorg's French entity Blocknodes SAS received full MiCA authorization from the AMF.The grant of MiCA authorization in March 2026 is confirmed by multiple independent outlets and the ESMA-sourced register.
    citedswissborg.com/blog/swissborg-secures-mic…-from-french-amfwww.coindesk.com/press-release/2026/03/1…arkets-authority
12. #22[confirmed][no action needed]in section: User Protections

    “SwissBorg publishes a Proof of Liabilities portal using a Merkle-tree cryptographic mechanism, allowing any user to verify that their balance is included in the platform's total reported liabilities. The open-source implementation is available on GitHub.”

    reviewerSwissBorg publishes a Proof of Liabilities portal using a Merkle-tree mechanism with an open-source implementation on GitHub.Repository exists and matches the described Merkle-tree verification approach, though the repo lacks an explicit open-source license file.
    citedgithub.com/SwissBorg/proof-of-liabilities
13. #24[confirmed][no action needed]in section: User Protections

    “The hack affected fewer than 1% of users and approximately 2% of total platform assets.”

    reviewerThe hack affected fewer than 1% of users and approximately 2% of total platform assets.Matches the cited company source and is repeated consistently in independent press coverage.
    citedswissborg.com/blog/sol-earn-incident-swissborg-recovery