- Home
- Security Audits
- Furucombo
Web3 · Smart Contract Audit
Furucombo Security Audits
softstack has completed 4 smart contract audits for Furucombo between April 2021 and September 2021, reporting 10 findings in total (3 medium, 3 low and 4 informational). Every report is published in the softstack public audit archive.
Key facts
- Client
- Furucombo
- Audits completed
- 4
- First audited
- Latest audit
- Chains
- Ethereum
- Languages
- Solidity
- Market cap
- $26,040 as of 2026-06-29
About the project
Furucombo is a DeFi aggregation protocol launched in 2020 that let users bundle actions across protocols such as Uniswap, Compound and Aave into a single Ethereum transaction. Its drag-and-drop interface represented each protocol action as a cube that could be chained into a combo. The consumer app has been retired, and the team now builds custom DeFi strategy infrastructure for businesses.
Findings
Combined across all 4 reviews softstack has completed for Furucombo. Each report is broken out below.
Reports
Newest first. Every report covers its own scope and commit.
Trevi smart contract audit
0Critical0High3Medium2Low4InformationalScope
Source repositorygithub.com/sushiswap/sushiswapComponents reviewed
14 modules · 18 files- AngelFactory.sol
- JoinPermit.sol
- HarvestPermit.sol
- FountainToken.sol
- ERC20FlashLoan.sol
- ERC20.sol
- ERC20Permit.sol
- Angel.sol
- FountainBase.sol
- AngelBase.sol
- Fountain.sol
- FountainFactory.sol
- Archangel.sol
- Harvest.sol
All 6 findings
ID Title Severity Status 5.1.4Wrong import of OpenZeppelin library Code Snippet Result/Recommendation In the current implementation, some OpenZeppelin files are part of the repository. This violates OpenZeppelin’s MIT license, which requires the license and copyright notice to
Low fixed 5.1.5Shadowing local variables Code Snippet Result/Recommendation In the current implementation, local variables are shadowing inherited state variables.
Low fixed 5.1.6Rename Sushi branding Code Snippet Result/Recommendation There are still branding from SushiSwap included, which would lead to confusion.
Informational fixed 5.1.7Public functions could be external Code Snippet Result/Recommendation In the current implementation several functions are declared as public where they could be external.
Informational fixed 5.1.8State variables should be constant Code Snippet Result/Recommendation In the current implementation two state variables are declared as immutable, where they should be constant. State variables can be declared as constant or immutable.
Informational fixed 5.1.9Checking for Boolean equality Code Snippet Result/Recommendation In the current implementation one require check uses a comparison to a Boolean constant. This leads to unnecessary gas consumption.
Informational fixed rCOMBO smart contract audit
0Critical0High0Medium1Low0InformationalScope
Components reviewed
2 modules · 2 files- GradualTokenSwap.sol
- RCOMBO.sol
(COMBO Token) smart contract audit
0Critical0High0Medium0Low0InformationalNo security findings reported.
Scope
Components reviewed
1 module · 1 file- COMBO.sol
Vesting Contract smart contract audit
0Critical0High0Medium0Low0InformationalNo security findings reported.
Scope
Components reviewed
1 module · 1 file- TokenVesting.sol
About this engagement
A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.
How softstack runs smart contract auditsMethodology
Review process
Scoping and threat modelling
The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.
Automated analysis
Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.
Manual code review
Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.
Adversarial testing
Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.
Reporting
Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.
Remediation verification
Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.
Standards and references
- SWC RegistrySmart Contract Weakness Classification
- CWECommon Weakness Enumeration
FAQ
Furucombo was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack has completed 4 smart contract audits for Furucombo between April 2021 and September 2021. The published reports are linked on this page and in the softstack public audit archive.
4 separate reviews, the first in April 2021 and the most recent in September 2021. Each one covers its own scope and commit, and is listed individually on this page.
10 findings across all 4 reviews: 3 medium, 3 low and 4 informational.
Each report covers the code as it stood at the commit it names, the most recent in September 2021. Any code changed after that point is outside the reviewed scope.
Related audits
Browse all security auditsDisclaimer
This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.