This audit report addresses a contract deployed on Arbitrum at 0x91c95440403263f60f71a2cdc8d1a824b6fbde33. Crucially, no source code was provided for analysis, rendering a comprehensive security assessment impossible. The lack of verified source code introduces significant and unquantifiable risks across all security domains, making any interaction with this contract highly speculative and dangerous. Users are strongly advised against interacting with unverified contracts.
Early-stage security check — honeypot & rug-pull analysis
Is Adapt a Scam?
Not verified
This record has not gone through deep verification and is not being monitored. The score is a dated snapshot — the token’s risk can change at any time.Own this token? Put it under verification →This audit report addresses a contract deployed on Arbitrum at 0x91c95440403263f60f71a2cdc8d1a824b6fbde33. Crucially, no source code was provided for analysis, rendering a comprehensive security assessment impossible.
Read the full analysis- Ownership status UNKNOWN
- Mint capability UNKNOWN
- Contract source not verified
- Top-10 concentration > 70%
- LP top1 unlocked holder = 100.0%
- LP top3 unlocked holders = 100.0%
- LP claimed locked but only 0.0% actually locked
- Token age < 24h
- 5 High finding(s) from audit
- 1 Low finding(s) from audit
Exact factors
- Ownership status UNKNOWN (owner could not be resolved)
- Mint capability UNKNOWN (implementation ABI unreadable)
- Contract source NOT verified
- Top-10 concentration > 70% (93.6% total → 93.6% effective; 93.6% in EOAs, 0.0% in contracts — extreme)
- LP top1 unlocked holder = 100.0% (independent LP — depth risk)
- LP top3 unlocked holders = 100.0% (independent LP — depth risk)
- LP claimed locked but only 0.0% actually locked
- Token age < 24h (brand new — bot activity, unproven)
- 5 High finding(s) from audit
- 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
Security Checklist
as of audit · Sep 4Holders
as of audit · Sep 4, 2026- Walletsanonymous holders, free to sell93.6%
- Everyone elsethe rest of the supply6.4%
How holder types affect the score
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.
Holder balances as recorded by the audit of Sep 4, 2026
Liquidity
as of audit · Sep 4The risk score reads depth across every pair.
The LP tokens of the analysed pool are locked or burned.
0x1d2a…158cNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
Security Findings
HighLack of Verified Source Code
The contract at 0x91c9…de33 does not have its source code verified on the block explorer. This prevents any form of security analysis, including architectural review (7.1 Architecture) and code security assessment (7.2 Code Security). Users are unable to confirm the contract's intended functionality or identify potential vulnerabilities.H-01
Issue
The contract at does not have its source code verified on the block explorer. This prevents any form of security analysis, including architectural review (7.1 Architecture) and code security assessment (7.2 Code Security). Users are unable to confirm the contract's intended functionality or identify potential vulnerabilities.
Fix
The contract deployer should immediately verify the full source code on the block explorer. This is a critical step for transparency, user trust, and enabling any form of security review.
Status
Unresolved
HighUnknown Contract Functionality and Security Posture
Due to the absence of verified source code, the actual functionality, business logic, and security posture of the contract remain entirely unknown. It is impossible to determine if the contract contains common vulnerabilities such as reentrancy, integer overflows/underflows, or other critical flaws (7.2 Code Security).H-02
Issue
Due to the absence of verified source code, the actual functionality, business logic, and security posture of the contract remain entirely unknown. It is impossible to determine if the contract contains common vulnerabilities such as reentrancy, integer overflows/underflows, or other critical flaws (7.2 Code Security).
Fix
Without verified source code, users should assume the contract's functionality is arbitrary and potentially malicious. Avoid any interaction with this contract until its source code is verified and thoroughly reviewed.
Status
Unresolved
HighUndeterminable Access Control Mechanisms
The access control mechanisms (7.3 Access Control) of the contract cannot be assessed without source code. It is unknown who has privileged access, what actions they can perform, and if these privileges are appropriately restricted. This could lead to unauthorized control over funds or critical contract functions.H-03
Issue
The access control mechanisms (7.3 Access Control) of the contract cannot be assessed without source code. It is unknown who has privileged access, what actions they can perform, and if these privileges are appropriately restricted. This could lead to unauthorized control over funds or critical contract functions.
Fix
Verify source code to allow for a proper assessment of access control. Implement robust, role-based access control with multi-signature requirements for critical operations.
Status
Unresolved
HighUndeterminable Upgradeability and Immutability
The upgradeability status (7.7 Upgrades) of the contract is unknown. It cannot be determined if the contract is immutable or if it implements an upgrade pattern (e.g., proxy). If upgradeable, the mechanism and control over upgrades are opaque, posing a high risk of malicious changes to the contract's logic post-deployment.H-04
Issue
The upgradeability status (7.7 Upgrades) of the contract is unknown. It cannot be determined if the contract is immutable or if it implements an upgrade pattern (e.g., proxy). If upgradeable, the mechanism and control over upgrades are opaque, posing a high risk of malicious changes to the contract's logic post-deployment.
Fix
If the contract is intended to be upgradeable, verify the source code to confirm the upgrade pattern and ensure upgradeability is controlled by a secure, multi-signature governance mechanism. If immutable, this should be verifiable from the source.
Status
Unresolved
HighUnassessable Economic and Governance Models
The economic model (7.4 Economic) and governance structure (7.5 Governance) of the contract cannot be evaluated. This prevents analysis of potential economic exploits, such as oracle manipulation, flash loan vulnerabilities, or centralized control over critical parameters. The contract's interaction with external protocols (7.6 External) is also unknown.H-05
Issue
The economic model (7.4 Economic) and governance structure (7.5 Governance) of the contract cannot be evaluated. This prevents analysis of potential economic exploits, such as oracle manipulation, flash loan vulnerabilities, or centralized control over critical parameters. The contract's interaction with external protocols (7.6 External) is also unknown.
Fix
Provide verified source code and comprehensive documentation detailing the economic model, governance structure, and any external dependencies. This is crucial for users to understand the financial risks and control mechanisms.
Status
Unresolved
LowAbsence of Public Audit Report
There is no publicly available security audit report for this contract. While not a direct vulnerability, the absence of an independent security review increases the overall risk profile, especially given the lack of verified source code.L-01
Issue
There is no publicly available security audit report for this contract. While not a direct vulnerability, the absence of an independent security review increases the overall risk profile, especially given the lack of verified source code.
Fix
Once source code is verified, engage reputable security auditors to conduct a thorough audit. Publish the audit report transparently for community review.
Status
Unresolved
Analysis
AI Copilotas of audit · Sep 4Without verified source code, a comprehensive technical security assessment (7.1 Architecture, 7.2 Code Security) is impossible. The contract's architecture, logic, and potential vulnerabilities like reentrancy, integer overflows, or access control flaws cannot be analyzed. This fundamental lack of transparency introduces significant technical risk, as the deployed bytecode's functionality remains entirely unknown and unauditable. No technical strengths can be identified without code.
The economic model (7.4 Economic) and governance mechanisms (7.5 Governance) of this contract cannot be determined without source code. This prevents any analysis of potential economic exploits, such as oracle manipulation, flash loan attacks, or unfair distribution of value. The absence of transparency makes it impossible to assess the contract's financial stability, its reliance on external protocols (7.6 External), or the control structures in place (7.3 Access Control).
The upgradeability status (7.7 Upgrades) of this contract is unknown without source code. It is impossible to determine if the contract is a proxy, if it uses a specific upgrade pattern (e.g., UUPS, Transparent), or if it is immutable. This lack of information poses a high risk, as malicious upgrade capabilities could be present, allowing for arbitrary changes to contract logic, potentially leading to asset loss or system compromise. No upgrade safety can be confirmed.
Interacting with smart contracts that lack verified source code on block explorers carries extreme risk.
Users cannot ascertain the contract's intended functionality, security posture, or potential for malicious behavior. It is strongly recommended to avoid deploying or interacting with contracts that do not have publicly verified source code, as this is a fundamental requirement for transparency and trust in the blockchain ecosystem. Always prioritize contracts with comprehensive documentation and independent security audits.
Contract & Record
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
- Aug 17, 2026100Critical
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Would You Like a More Detailed Audit of Adapt?
This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.
Get Detailed Audit Is this your token? Publish your own audit on this page