Use complementary methods
Manual review and automated tools surface different failure modes. I used them together rather than treating one scanner as the audit.
Case 07 · Smart contract security
Smart contract security for crypto exchanges and DeFi protocols.
FearsOff is a cybersecurity company providing Web3 security services. I worked as a smart contract auditor on exchange contracts, DeFi integrations and AMM liquidity logic, reviewing attack paths and delivering findings with remediation guidance to the engineering teams.
Delivered audits and remediation guidance for engagements covering Crypto.com exchange contracts, HTX integration modules and Smardex AMM and liquidity contracts.
The reviews covered different ways funds could be affected: privileged actions in exchange contracts, assumptions at DeFi integration boundaries and balance accounting in AMM liquidity operations.
Reviewed contract behavior, authorization boundaries and paths that affect assets.
Used Slither, Mythril, Echidna and Manticore, with formal verification techniques on critical functions.
Delivered findings with remediation and gas-optimization guidance for engineering teams.
Identify the assets, privileged roles and state transitions that define the contract’s trust boundaries.
Assets + permissions + state transitionsThe review starts from what must remain true.Combine manual reasoning with automated tools to search for paths that violate those assumptions.
Manual review + adversarial testsTool output needs interpretation in the contract’s context.Connect a suspected issue to a specific affected asset, permission or accounting path and prioritize its consequence.
Issue → reachable behavior → impactA finding must explain why the behavior matters.Translate the technical finding into concrete implementation guidance for the team responsible for the contract.
Finding + remediation recommendationThe report must be usable by the engineers fixing the code.Manual review and automated tools surface different failure modes. I used them together rather than treating one scanner as the audit.
Reports connect the issue, consequence and proposed remediation so the delivery team can act on them.
Client scope and methods are recorded in my CV. Engagements were performed through FearsOff.
Official service scope. Client names and my audit scope come from my career record; individual reports remain confidential.
Engagements delivered through FearsOff, as documented in my CV; the named organizations describe audit scope.
Audit reports and vulnerability details remain confidential.