CertiK reviewed Cylum Finance on 19 Apr 2022: 5 findings, 0 critical; none marked fixed.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 3 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 2 | 0 | 0 |
In the contract `CYLUM` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority. 
All of the CYM tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute CYM tokens without obtaining the consensus of the community.
The contract is serving as the underlying entity to interact with third party ILockContract. The scope of the audit treats 3rd party entities as black boxes and assume their functional correctness. However, in the real world, 3rd parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of 3rd parties can possibly create severe impacts, such as increasing fees of 3rd parties, migrating to new LP pools, etc.
There should always be events emitted in the sensitive functions that are controlled by centralization roles.
Function `_transferFromExcluded`, `_transferToExcluded`, `_transferBothExcluded` can all be replaced by `_transferNoFee`.
| Address | Chain | Source code |
|---|---|---|
| 0x15ea…56fe0x15ea6b8481bf1c991ac3dc8e67279d31651a56fe | Chain: BNB Chain | Source code: Verified source |
1,045 projects reviewed · 1,376 reports · latest May 2025
See CertiK’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us