Smart Contracts Security Testing
While doing the assessment, we include automated checks, however, smart contracts hacking relies more on logical issues, we are focusing a lot on manual analysis. Check below a list of examples of impactful vulnerabilities that we are hunting (and found!) while doing a Smart Contract Security Audit:
Suicidal Attack
Fund Lockout Attack
Reentrancy
Broken Access Controls (Ownership Attacks)
Frontrunning
Manipulation of Transfers
Insecure Delegate Calls
Replay Attacks
Tampering of Emergency Withdraw
Timestamp Manipulation
Insecure Low-Level Calls
Prediction of Random Number Generators (RNG)
Why is it important to audit the security of your Smart Contract?
Once you deploy them, it is very hard to make any changes, because they are immutable by default. It means that you should focus on the whole security aspect of the project before actually going live.
They are 100% transparent for everyone. Attackers can view the full source code of the smart contracts by just knowing the address on the blockchain network. This allows them to analyze every piece of code possible, and possibly find exploitable vulnerabilities.
The smart contract represents the whole operation logic of your project, being responsible for sensitive actions, such as crypto transfers. It is similar to Core Banking Systems (which are commonly very protected and unexposed), but the Smart Contract code is available to everyone.
Our Methodology for Smart Contracts Security Testing
Our methodology when auditing a smart contract is split into three parts
Architecture & Data Flow Document Review
Static Source Code Analysis
Dynamic Smart Contract Security Testing with Deployment on Local/Test Blockchain Networks