CYBRO
  • Introduction
  • πŸš€CYBRO Product
    • What is CYBRO?
    • Product Roadmap
    • Team and Principles
    • Governance
    • What CYBRO isn't
    • Smart Contracts Addresses
    • How to integrate?
  • πŸͺ™$CYBRO Token
    • About $CYBRO
    • Claiming
    • Bridging
    • Staking
    • Official Addresses
    • Tokenomics
    • CYBRO Points
    • 🌟Referral Program
    • How To Buy
    • Presale
  • πŸ§‘β€βš–οΈTransparency
    • Security Audits
    • Reports
      • Security report / 29th May 2025
      • Governance report / 8th May 2025
      • Governance report / 5th May 2025
      • Governance report / 30th April 2025
      • Governance report / 21st April 2025
      • Governance report / 14th April 2025
      • Governance report / 8th April 2025
      • Governance report / 2nd April 2025
      • Governance report / 2nd April 2025
      • Governance report / 1st April 2025
      • Governance report / 24th March 2025
      • Governance report / 21st March 2025
      • Governance report / 21st March 2025
      • Governance report / 19th March 2025
      • Governance report / 18th March 2025
      • Governance report / 17th March 2025
      • Governance report / 13th March 2025
      • Governance report / 6th March 2025
      • Governance report / 3rd March 2025
      • Governance report / 25th February 2025
      • Governance report / 18th February 2025
      • Governance report / 11th February 2025
      • Governance report / 10th February 2025
      • Governance report / 4th February 2025
      • Governance report / 28th January 2025
      • Governance report / 23rd January 2025
      • Governance report / 22nd Janyary 2025
      • Governance report / 16th January 2025 #2
      • Governance report / 16th January 2025
      • Governance report / 15th January 2025
      • Governance report / 14th January 2024
      • Governance report / 9th January 2025
      • Governance report / 7th January 2025
      • Governance report / 29th December 2024
      • Governance report / 26th December 2024
      • Governance report / 25th December 2024
      • Governance report / 25th December 2024
      • Governance report / 24th December 2024
      • Governance report / 23rd December 2024
      • Governance report / 17th December 2024
      • Governance report / 14th December 2024
      • Governance report / 14th December 2024
      • Governance report / 14th December 2024
      • Governance report / 11th December 2024
      • Governance report / 11th December 2024
      • Governance report / 10th December 2024
      • Governance report / 10th December 2024
      • Governance report / 7th December 2024
      • Governance report / 4th December 2024
      • Governance report / 4th December 2024
      • Governance report / 3rd December 2024
      • Governance report / 3rd December 2024
      • Governance report / 2nd December 2024
      • Governance report / 22nd November 2024
      • Governance report / 21st November 2024
      • Governance report / 19th November 2024
      • Governance report / 18th November 2024
      • Governance report / 18th November 2024
      • Governance report / 15th November 2024
      • Governance report / 12th November 2024
      • Governance report / 7th November 2024
      • Governance report / 30th October 2024
      • Governance report / 24th October 2024
      • Governance report / 21st October 2024
      • Governance report / 16th October 2024
      • Governance report / 15th October 2024
      • Governance report / 10th October 2024
      • Governance report / 3rd October 2024
      • Governance report / 27th September 2024
      • Governance report / 25th September 2024
      • Governance report / 23rd September 2024
      • Governance report / 20th September 2024
      • Governance report / 19th September 2024
      • Governance report / 18th September 2024
      • Governance report / 13th September 2024
      • Governance report / 11th September 2024
      • Governance report / 5th September 2024
      • Governance report / 2nd September 2024
      • Governance report / 27th August 2024
      • Governance report / 26th August 2024
      • Governance report / 21th August 2024
      • Governance report / 14th August 2024
      • Governance report / 13th August 2024
      • Governance report / 5th August 2024
      • Governance report / 1st August 2024
      • Governance report / 31th July 2024
      • Governance report / 24th July 2024
      • Governance report / 17th July 2024
      • Governance report / 16th July 2024
      • Governance report / 11th July 2024
      • Governance report / 10th July 2024
      • Security report / 9th July 2024
      • Governance report / 3rd July 2024
      • Governance report / 18th June 2024
      • Governance report / 4th June 2024
      • Governance report / 29th May 2024
      • Governance report / 20th May 2024
      • Governance report / 15th May 2024
      • Security report / 10th May 2024
      • Governance report / 8th May 2024
      • Governance report / 1st May 2024
      • Security report / 1st May 2024
      • Governance report / 19th April 2024
      • Governance report / 12th June 2024
      • Governance report / 26th June 2024
      • Governance report / 25th December 2024
    • Bug Bounty
  • ❓HELP & FAQ
    • Official links
    • FAQ
Powered by GitBook
On this page
  1. Transparency
  2. Reports

Security report / 29th May 2025

Bug-related loss of funds in 3 vault contracts

Due to a bug in three Vault contracts discovered on the 21st May 2025, some user deposits were lost, with a total value of $18,612.93. The CYBRO team will fully refund the affected users using funds from the project treasury. The contracts had previously been audited by QuillAudits.

Affected Vaults

  • BlasterSwap V2 (USDB/WETH): $12,765.49

  • BladeSwap (USDB/WETH): $5,456.74

  • Camelot V3 + GAMMA (ETH/USDC): $390.70

Refunds will be issued directly to users' wallets by the end of May, in USDC on the same chain where the Vault was deployed.


What happened

On May 23rd, a user reported an incorrect balance in the CYBRO dApp. Unusual on-chain activity was detected in several CYBRO’s Vaults, and the CYBRO team quickly identified a bug. The auditors at QuillAudits supported the investigation and promptly assigned an additional investigator from Merkle to assist.

It appears that some users may have exploited the vulnerability to steal funds from the affected Vaults. The investigation is ongoing, and we will report our findings to the appropriate authorities once complete.

The vulnerable contracts were promptly shut down, new deposits were halted, and the team conducted a thorough multi-day investigation.

Other contracts are safe, the CYBRO token contract is also safe.

CryptoCrouton CYBRO Project Lead

PreviousReportsNextGovernance report / 8th May 2025

Last updated 18 hours ago

πŸ§‘β€βš–οΈ