Is CryptoAutos (AUTOS) Safe? Smart Contract Security Analysis

Security Findings

1 Low

Low

Redundant SafeMath Library with Potentially Less Secure Functions

L-01The `SafeMath` library is included in the codebase, but the `ERC20` contract primarily uses native Solidity 0.8.0+ arithmetic operations, often within `unchecked` blocks that are safely guarded by `require` statements. This makes the `SafeMath` library largely redundant. Furthermore, some `SafeMath` functions (e.g., `add`, `sub`, `mul`, `div`, `mod` without `try` or `errorMessage` parameters) explicitly use `unchecked` blocks without adding their own overflow/underflow checks, making them less secure than native operations in Solidity 0.8.0+ where checks are default. While the `ERC20` contract does not directly use these specific problematic `SafeMath` functions, their presence adds unneces…

IssueThe `SafeMath` library is included in the codebase, but the `ERC20` contract primarily uses native Solidity 0.8.0+ arithmetic operations, often within `unchecked` blocks that are safely guarded by `require` statements. This makes the `SafeMath` library largely redundant. Furthermore, some `SafeMath` functions (e.g., `add`, `sub`, `mul`, `div`, `mod` without `try` or `errorMessage` parameters) explicitly use `unchecked` blocks without adding their own overflow/underflow checks, making them less secure than native operations in Solidity 0.8.0+ where checks are default. While the `ERC20` contract does not directly use these specific problematic `SafeMath` functions, their presence adds unneces…

FixConsider removing the `SafeMath` library entirely, as Solidity 0.8.0+ provides native overflow/underflow protection by default, and the contract's current use of `unchecked` blocks with `require` statements is a secure and efficient pattern. If `SafeMath` is intended for specific `try*` functions, ensure only those are used and the redundant `add`/`sub`/`mul`/`div`/`mod` functions are removed.

StatusUnresolved

Category Ratings

TechnicalLow10/10

The contract implements a standard ERC-20 token, utilizing Solidity 0.8.28 features where arithmetic operations within `unchecked` blocks are safely guarded by `require` statements, demonstrating robust code security (7.2 Code Security). For example, `_transfer` ensures `fromBalance >= amount` before `unchecked` subtraction. The inclusion of the `SafeMath` library is largely redundant for Solidity 0.8.0+ and some of its functions are less safe than native operations, though not directly used by the `ERC20` logic.

GovernanceLow10/10

Governance risk is low as external data indicates the contract ownership has been renounced, removing centralized control over administrative functions (7.5 Governance). This decentralization enhances trust. Economic risk is also low due to long-term liquidity locks with UNCX V2 until 2050, which significantly reduces the potential for rug pulls and enhances token stability (7.4 Economic).

UpgradesLow10/10

The contract is not designed as a proxy and is therefore not upgradeable (7.7 Upgrades). This eliminates upgrade-related risks such as proxy implementation vulnerabilities or administrative key compromise, providing a fixed and immutable contract state.

Security Checklist

5/5 checks passed

Contract VerifiedPass

Ownership RenouncedPass

No Mint FunctionPass

Liquidity LockedPass

Not a ProxyPass

HoneypotNoneBuy Tax0.0%Sell Tax0.0%

Holder Composition

38.5% in top 10

5.4% in wallets33.1% in contracts

Effective Concentration18.6%

Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.

Liquidity Depth

$126.5K

The risk score reads depth across every pair. The volume figure and the volume-to-liquidity ratio elsewhere on this page describe only the pair this audit analysed, so the two are not directly comparable.

LP Distribution

LP Locked100.0% · Null Address, UNCX

Lock Expiry2050 (verified ≥ 1 year) · UNCX V2

Key Addresses

1 addresses

Deployer

0xef72…1fc6

What Raised This Score

1 factors

1 Low finding(s) from audit

Each factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed

Not Signed In

Is CryptoAutos Safe?