Quantum Audit Logo

Is TrustCat a Scam?

Early-stage security check — honeypot & rug-pull analysis

Is this your token? Publish your own audit on this page →

TrustCat TRUSTCAT
0x75b3…7777
BNB Chain Not verifiedLast checked 1d ago 1 audit on record New Launch · 1d old
DexScreener ↗
How is this score calculated? → Low Risk
Executive SummaryAI Copilot

This report is generated without access to the smart contract source code. Therefore, a comprehensive security audit could not be performed. The findings below reflect the inability to conduct a proper analysis rather than specific vulnerabilities within the contract. All risk levels are set to 'Low' by default due to the absence of code for evaluation.

3 Informational
! Early-stage analysis. This token has limited on-chain history (1d old). New tokens carry elevated risk — data may change rapidly. Always verify independently before investing.
Volume 24h
$664.4K
Liquidity
$67.8K
Price
$0.0004113
Token Age
1d
Top 10 Holders
28.4%

Security Findings

3 Info
Info

No Contract Source Code Provided

I-01The audit was requested for a contract address (0x75b3…7777) on the BSC network, but no corresponding Solidity source code was provided for analysis. This prevents any meaningful security assessment of the contract's implementation.
IssueThe audit was requested for a contract address () on the BSC network, but no corresponding Solidity source code was provided for analysis. This prevents any meaningful security assessment of the contract's implementation.
FixAlways provide the full and verified source code for all contracts intended for audit. This includes all dependent libraries and imported contracts. Ensure the provided source code matches the deployed bytecode on the blockchain.
StatusUnresolved
Info

Inability to Assess Technical Security

I-02Without the source code, it is impossible to evaluate critical technical security aspects such as reentrancy vulnerabilities, integer overflows/underflows, access control flaws (7.3 Access Control), potential denial-of-service vectors, or adherence to secure coding best practices (7.2 Code Security). The contract's architecture (7.1 Architecture) also remains unverified.
IssueWithout the source code, it is impossible to evaluate critical technical security aspects such as reentrancy vulnerabilities, integer overflows/underflows, access control flaws (7.3 Access Control), potential denial-of-service vectors, or adherence to secure coding best practices (7.2 Code Security). The contract's architecture (7.1 Architecture) also remains unverified.
FixEnsure that all smart contracts are developed following established security patterns and best practices. Conduct thorough internal code reviews and static analysis before submitting for external audit. Focus on robust input validation, secure state transitions, and proper error handling.
StatusUnresolved
Info

Inability to Assess Economic and Governance Risks

I-03The absence of source code precludes any analysis of the contract's economic model (7.4 Economic), including tokenomics, fee structures, and incentive mechanisms. Similarly, the governance framework (7.5 Governance) and its associated risks, such as centralized control or upgrade path vulnerabilities (7.7 Upgrades), cannot be assessed.
IssueThe absence of source code precludes any analysis of the contract's economic model (7.4 Economic), including tokenomics, fee structures, and incentive mechanisms. Similarly, the governance framework (7.5 Governance) and its associated risks, such as centralized control or upgrade path vulnerabilities (7.7 Upgrades), cannot be assessed.
FixDesign economic models with careful consideration of potential attack vectors and long-term sustainability. Implement transparent and decentralized governance mechanisms where appropriate. For upgradeable contracts, ensure the upgrade process is secure, well-documented, and communicated to users.
StatusUnresolved

Category Ratings

TechnicalLow10/10

Without the contract's source code, a detailed technical assessment of 7.1 Architecture, 7.2 Code Security, and 7.3 Access Control cannot be performed. Key areas like reentrancy protection, integer overflow/underflow, and proper access control mechanisms could not be verified. Adherence to secure coding practices is paramount for smart contract integrity.

GovernanceLow9/10

The economic model (7.4 Economic) and governance structure (7.5 Governance) of the protocol could not be evaluated due to the absence of source code. This prevents analysis of tokenomics, fee structures, incentive mechanisms, and decision-making processes. Robust economic design and transparent governance are crucial for long-term protocol stability and user trust.

UpgradesLow10/10

An assessment of the upgradeability mechanism (7.7 Upgrades) was not possible without the contract's source code. This includes verifying the use of secure proxy patterns (e.g., UUPS, Transparent) and ensuring proper initialization and storage slot management. Secure upgrade paths are vital for future protocol evolution and bug fixes.

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

28.4% in top 10
5.8% in wallets22.5% in contracts
Effective Concentration14.8%

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

$67.8K

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 Burned100.0% · ≈ permanent lock
LP Locked100.0% · Null Address

Key Addresses

1 addresses
Deployer
0x55b0…27ab

What Raised This Score

1 factors
  • Token age < 7 days (early, volatile)

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

Related Audits

6 more on the record
TCryptochicks (TCC)Low Risk币安人生Low RiskSKYAILow RiskBLow RiskDOYRLow RiskCREPELow Risk

Would You Like a More Detailed Audit of TrustCat?

This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.

Get Detailed Audit