Introduction
We express our gratitude to the daCAT team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
daCat is an ERC20 token with burning and anti-bot sniping features.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for daCAT |
| Audited By | Arda Usman, David Camps |
| Approved By | Ivan Bondar |
| Website | https://dacat.fun/→ |
| Changelog | 03/09/2025 - Preliminary Report |
| 04/09/2025 - Final Report | |
| Platform | Ethereum |
| Language | Solidity |
| Tags | ERC20 |
| Methodology | https://hackenio.cc/sc_methodology→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for daCAT
- Audited By
- Arda Usman, David Camps
- Approved By
- Ivan Bondar
- Website
- https://dacat.fun/→
- Changelog
- 03/09/2025 - Preliminary Report
- 04/09/2025 - Final Report
- Platform
- Ethereum
- Language
- Solidity
- Tags
- ERC20
- Methodology
- https://hackenio.cc/sc_methodology→
Review Scope | |
|---|---|
| Repository | https://etherscan.io/address/0x814a870726edb7dfc4798300ae1ce3e5da0ac467#code→ |
| Commit | n/a |
Review Scope
- Commit
- n/a
Audit Summary
The system users should acknowledge all the risks summed up in the risks section of the report
Documentation quality
Functional requirements are provided.
Technical description is provided.
Code quality
The code mostly follows best practices and style guides.
See informational findings for more details.
The development environment is not configured.
Test coverage
Code coverage of the project is 0.0% (branch coverage),
No tests provided.
System Overview
daCat is an ERC20 token with burning and anti-bot sniping features. It has the following contract:
daCat — simple ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed.
It has the following attributes:
Name: daCat
Symbol: daCat
Total supply: 420,690,000,000,000 tokens.
Privileged roles
The owner of the daCat contract can enable trading for other users.
The owner and the bridge contract can transfer tokens without restrictions.
Potential Risks
In the daCat token contract, the burnFrom function is publicly accessible, allowing any address with an approved allowance to burn tokens from the specified account. This introduces a risk of unintended or excessive token burns, potentially resulting in loss of user funds if the spender is malicious or misuses the allowance.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2025-1259 | Potential Denial of Service on Token Sells | mitigated | Medium | |
| F-2025-1261 | Repeated Calls to enableTrading() Allow Market Manipulation | mitigated | Low | |
| F-2025-1260 | Restrictive Gas Price Limit | mitigated | Low | |
| F-2025-1260 | Large Token Burns Blocked by Anti-Bot Measures | mitigated | Low | |
| F-2025-1260 | Missing Events for Key State Changes | accepted | Observation | |
| F-2025-1260 | Use Ownable2Step to Prevent Accidental Ownership Loss | mitigated | Observation | |
| F-2025-1260 | Redundant and Unused Code | accepted | Observation |
Appendix 1. Definitions
Severities
When auditing smart contracts, Hacken is using a risk-based approach that considers Likelihood, Impact, Exploitability and Complexity metrics to evaluate findings and score severities.
Reference on how risk scoring is done is available through the repository in our Github organization:
Severity | Description |
|---|---|
Critical | Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation. |
High | High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation. |
Medium | Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category. |
Low | Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution. |
Severity
- Critical
Description
- Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation.
Severity
- High
Description
- High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation.
Severity
- Medium
Description
- Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category.
Severity
- Low
Description
- Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution.
Potential Risks
The "Potential Risks" section identifies issues that are not direct security vulnerabilities but could still affect the project’s performance, reliability, or user trust. These risks arise from design choices, architectural decisions, or operational practices that, while not immediately exploitable, may lead to problems under certain conditions. Additionally, potential risks can impact the quality of the audit itself, as they may involve external factors or components beyond the scope of the audit, leading to incomplete assessments or oversight of key areas. This section aims to provide a broader perspective on factors that could affect the project's long-term security, functionality, and the comprehensiveness of the audit findings.
Appendix 2. Scope
The scope of the project includes the following smart contracts from the provided repository:
Scope Details | |
|---|---|
| Repository | https://etherscan.io/address/0x814a870726edb7dfc4798300ae1ce3e5da0ac467#code→ |
| Commit | n/a |
| Whitepaper | https://whitepaper.dacat.fun→ |
| Requirements | https://dacat.fun→ |
| Technical Requirements | https://dacat.fun→ |
Scope Details
- Commit
- n/a
- Whitepaper
- https://whitepaper.dacat.fun→
- Requirements
- https://dacat.fun→
- Technical Requirements
- https://dacat.fun→
Assets in Scope
Appendix 3. Additional Valuables
Additional Recommendations
The smart contracts in the scope of this audit could benefit from the introduction of automatic emergency actions for critical activities, such as unauthorized operations like ownership changes or proxy upgrades, as well as unexpected fund manipulations, including large withdrawals or minting events. Adding such mechanisms would enable the protocol to react automatically to unusual activity, ensuring that the contract remains secure and functions as intended.
To improve functionality, these emergency actions could be designed to trigger under specific conditions, such as:
Detecting changes to ownership or critical permissions.
Monitoring large or unexpected transactions and minting events.
Pausing operations when irregularities are identified.
These enhancements would provide an added layer of security, making the contract more robust and better equipped to handle unexpected situations while maintaining smooth operations.