Unilab-Network 1012022SCAudit Report 2
Unilab-Network 1012022SCAudit Report 2
Unilab-Network 1012022SCAudit Report 2
Document
Name Smart Contract Code Review and Security Analysis Report for
Unilab Network.
Approved by Andrew Matiukhin | CTO Hacken OU
Type ERC20 token; Transfer controller
Platform Ethereum / Solidity
Methods Architecture Review, Functional Testing, Computer-Aided
Verification, Manual Review
Repository https://github.com/unilabnetwork/unilab-for-
audits/blob/master/ERC20SupportingFeesInQuoteToken.sol
Commit 0DB13F0964E0ED6A8A25714DD872C7D497F1C788
Technical NO
Documentation
JS tests NO
Website unilab.network
Timeline 27 DECEMBER 2021 - 11 JANUARY 2022
Changelog 05 JANUARY 2022– INITIAL AUDIT
11 JANUARY 2022– SECOND REVIEW
www.hacken.io
Table of contents
Introduction 4
Scope 4
Executive Summary 5
Severity Definitions 6
Audit overview 7
Conclusion 8
Disclaimers 9
www.hacken.io
Introduction
Hacken OÜ (Consultant) was contracted by Unilab Network (Customer) to conduct
a Smart Contract Code Review and Security Analysis. This report presents the
findings of the security assessment of the Customer's smart contract and its
code review conducted between December 27th, 2021 - January 5th, 2022.
The second review was provided on January 11th, 2022.
Scope
The scope of the project is smart contracts in the repository:
Repository:
https://github.com/unilabnetwork/unilab-for-
audits/blob/master/ERC20SupportingFeesInQuoteToken.sol
Commit:
0db13f0964e0ed6a8a25714dd872c7d497f1c788
Technical Documentation: No
JS tests: No
Contracts:
ERC20SupportingFeesInQuoteToken.sol
We have scanned this smart contract for commonly known and more specific
vulnerabilities. Here are some of the commonly known vulnerabilities that
are considered:
Category Check Item
Code review ▪ Reentrancy
▪ Ownership Takeover
▪ Timestamp Dependence
▪ Gas Limit and Loops
▪ DoS with (Unexpected) Throw
▪ DoS with Block Gas Limit
▪ Transaction-Ordering Dependence
▪ Style guide violation
▪ Costly Loop
▪ ERC20 API violation
▪ Unchecked external call
▪ Unchecked math
▪ Unsafe type inference
▪ Implicit visibility level
▪ Deployment Consistency
▪ Repository Consistency
▪ Data Consistency
www.hacken.io
Functional review
▪ Business Logics Review
▪ Functionality Checks
▪ Access Control & Authorization
▪ Escrow manipulation
▪ Token Supply manipulation
▪ Assets integrity
▪ User Balances manipulation
▪ Data Consistency manipulation
▪ Kill-Switch Mechanism
▪ Operation Trails & Event Generation
Executive Summary
According to the assessment, the Customer's smart contracts are well-secured.
www.hacken.io
Severity Definitions
Risk Level Description
Critical vulnerabilities are usually straightforward to
Critical exploit and can lead to assets loss or data
manipulations.
High-level vulnerabilities are difficult to exploit;
however, they also have a significant impact on smart
High
contract execution, e.g., public access to crucial
functions
Medium-level vulnerabilities are important to fix;
Medium however, they can't lead to assets loss or data
manipulations.
Low-level vulnerabilities are mostly related to
Low outdated, unused, etc. code snippets that can't have
a significant impact on execution
www.hacken.io
Audit overview
Critical
No critical issues were found.
High
No high severity issues were found.
Medium
No medium severity issues were found.
Low
No low severity issues were found.
www.hacken.io
Conclusion
Smart contracts within the scope were manually reviewed and analyzed with
static analysis tools.
The audit report contains all found security vulnerabilities and other issues
in the reviewed code.
As a result of the audit, security engineers found no severity issues.
As a result of the second audit, security engineers found no severity issues.
Notice:
botProtection contract can impact token transfers. This contract is out of
the scope of the audit.
www.hacken.io
Disclaimers
Hacken Disclaimer
The smart contracts given for audit have been analyzed in accordance with
the best industry practices at the date of this report, in relation to
cybersecurity vulnerabilities and issues in smart contract source code, the
details of which are disclosed in this report (Source Code); the Source Code
compilation, deployment, and functionality (performing the intended
functions).
The audit makes no statements or warranties on the security of the code. It
also cannot be considered as a sufficient assessment regarding the utility
and safety of the code, bug-free status, or any other statements of the
contract. While we have done our best in conducting the analysis and producing
this report, it is important to note that you should not rely on this report
only — we recommend proceeding with several independent audits and a public
bug bounty program to ensure the security of smart contracts.
Technical Disclaimer
www.hacken.io